Hi Glenn,
I must say I a bit stumped by this so I've CC'd it to the PostgreSQL
Interfaces mailing list in the hopes that someone there may have an idea
whats happening.
The obvious (and perhaps condescending!) question has to be: are you sure
you are trying to access the same database you migrated to?
I'm assuming that is the case, so could you re-run the migration with the
ODBC drivers commlog option switched on and send me the logfile created so I
can see if there is anything odd happening.
Regards,
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
> -----Original Message-----
> From: Glenn Howe [mailto:ghowe1@tampabay.rr.com]
> Sent: 11 April 1999 19:35
> To: Dave Page
> Subject: Problem migrating MSAccess97 table
>
>
> Hello,
>
> I am able to add tables and modify etc, using pgadmin on a
> database that
> resides on a linux box. That works great. I can then access
> those tables via
> psql or perl DBI.
>
>
> the problem is when I migrate an access .mdb file. It does
> the migration
> just fine and using pgadmin I can access the newly created
> postgres tables
> just fine, I can see the data etc. But, if I use psql or
> perl dbi, it tells
> me the table does not exist.
>
> What am I doing wrong. I have tried checking and unchecking
> all the odbc
> driver boxes and trying it again. is there a procedure to
> read regardind
> migrating access 97 tables.
>
>
> <>< ==================
> Glenn Howe
> Network Engineer, MCSE
> 813.651.2700
> MAILTO:ghowe1@tampabay.rr.com
> HomePage: http://home.tampabay.rr.com/tgh
>
