RE: [INTERFACES] pgAdmin connection error on NT and W98 - Mailing list pgsql-interfaces

From Nicolas Huillard
Subject RE: [INTERFACES] pgAdmin connection error on NT and W98
Date
Msg-id 01BF213A.BC075480@agen.int.ghs
Whole thread Raw
List pgsql-interfaces
OK, it works fine, but the data is not copied, because of the large binary objects (the message is quite clear).
I will look at ftp://ftp.sdc.com.au/pub/repl for "a general purpose database replicator for any pair of databases which
inderstandODBC" (as posted in this list by Stephen Davies).
 

The last (I hope) problem is due to database protection : my Access databases are password protected, by an Access
Workgroup(MDW file). pgAdmin says it can't access the database, even if I type the right Username/Password in the
DatabaseMigration Wizard. The message is :
 

Error Details
*************
Error No: 3033
Error Description: You don't have the necessary permissions to use the
'C:\Donnees\G.H.S\Creation\Nutrigest\Développement\Bases\InternetNutrigest admin.mdb' object.  Have your system
administratoror the person who created this object establish the appropriate permissions for you.
 
Error Source: DAO.Workspace
DLL Error Code: 0

TIA,

Nicolas Huillard

-----Message d'origine-----
De:    Dave Page [SMTP:dpage@vale-housing.co.uk]
Date:    jeudi 28 octobre 1999 11:04
À:    'Nicolas Huillard'
Cc:    'pgsql-interfaces@postgresql.org'
Objet:    RE: [INTERFACES] pgAdmin connection error on NT and W98

> -----Original Message-----
> From: Nicolas Huillard [mailto:nhuillard@ghs.fr]
> Sent: 27 October 1999 09:34
> To: 'Dave Page'
> Cc: 'pgsql-interfaces@postgresql.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:

Previous
From: Alain TESIO
Date:
Subject: Re: [INTERFACES] Replication between MS Access and PostgreSQL
Next
From: "Fabio.di.Fabio"
Date:
Subject: Uppercase problem with several interfaces