Hi Joshua,
thanks for the link. I'm not getting that error anymore, but now I'm getting a problem when I'm importing several tables with the error "the size of a field is too long". As far as I remember, the tables only compose of int4 fields, varchar fields and a text field.
Text boxe's don't have a limit on the number of charecters they are stored as they are seen as a string. This leads me to believe that it's the varchar fields, since the highest number in the integer fields is 7759. Any ideas on what's going wrong? Any ideas what the maximum number of charecters is allowed for varchar fields? At the moment, I have specified the limit for number of charecters in the varchar fields.
Cheers,
Ben
On 8/1/06, Joshua D. Drake <jd@commandprompt.com> wrote:ben sewell wrote:
> Hi,
> I'm running a postgresql 8.1 server on Windows 2002 Small Business
> Server. I
> am in the middle of a migration from an MS Access backend to a PostgreSQL
> backend. The existing MS Access 2000 frontend will be used. I'm using the
> pgSQL ODBC driver (latest) on Windows XP Pro SP2.
You could try ODBCng:
http://projects.commandprompt.com/public/odbcng
Joshua D. Drake
>
> I have using the linked table wizzard to link tables to the PostgreSQL,
> which had no problems and I setup the relationships on the front end.
> However, when I try to open the database, it is saying this error message
> "ODBC--connection to '{PostgreSQL}10.0.0.2' failed". This is strange
> because
> I can ping the server and use telnet to connect to postgresql. I've done a
> google search and this seems to be a problem that seems to happen to MySQL
> databases. What I was wondering is, can anyone offer any solutions on
> how to
> solve this problem?
>
> Cheers,
> Ben
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/