Skip site navigation (1) Skip section navigation (2)

RE: [INTERFACES] pgAdmin connection error on NT and W98

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Nicolas Huillard'" <nhuillard(at)ghs(dot)fr>
Cc: "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: [INTERFACES] pgAdmin connection error on NT and W98
Date: 1999-10-28 09:04:19
Message-ID: 8568FC767B4AD311AC33006097BCD3D60142AD@woody.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-interfaces
> -----Original Message-----
> From: Nicolas Huillard [mailto:nhuillard(at)ghs(dot)fr]
> Sent: 27 October 1999 09:34
> To: 'Dave Page'
> Cc: 'pgsql-interfaces(at)postgresql(dot)org'
> Subject: RE: [INTERFACES] pgAdmin connection error on NT and W98
> 
> The Migration error was about an OLE field in the Access 
> database (s_Lineage). Which is converted in a blank field 
> type. See the log file :
>  
I have tested pgAdmin with OLE fields in an Access MDB, and they seem to
work correctly on my system (that is, the table is created, but the
Migration Wizard cannot migrate blob data and will ignore it). My guess is
that you do not have the lo datatype configured on your PostgreSQL system.
If this is the case, you can create it with the following SQL:

CREATE TYPE "lo" ( internallength = 4, 
                   externallength = 10, 
                   input = int4in, 
                   output = int4out, 
                   send = int4out, 
                   receive = int4in, 
                   default = '',
                   passedbyvalue);

 
Regards,
 
Dave.
 
-- 
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
    


pgsql-interfaces by date

Next:From: InaDate: 1999-10-28 09:04:21
Subject: Insertion Error
Previous:From: Alain.TesioDate: 1999-10-28 07:46:26
Subject: Re: [INTERFACES] Replication between MS Access and PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group