Re: dropped columns and ms access

"Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch> wrote in message
news:6C0CF58A187DA5479245E0830AF84F42080336(at)poweredge(dot)attiksystem(dot)ch(dot)(dot)(dot)
>I'm not aware of a problem like that, really. Personnally, after each
change to the backend, I relink all tables, programmatically. Here is the
code:

Thanks,

I'm getting close to deploying an app at my office. Programmatically
relinking will make deployment easier for my employees, without having
everyone navigate menus and the Data Sources applet in Control Panel.

My current problem isn't with the relinking process, but with creating new
links after table structure modification. I got the dreaded #NAME? field
contents odbc error after changing a few table structures, primarily
deleting columns. No previous problems when columns were added. The cause
was not apparent until I found some threads related to this issue, actually
in this list, back in 12/2002 through 2/2003.

My normal sequence of events after a table modification on the backend is to
delete the previous link, then create a new link. The problems showed up
after this sequence, with the error described above.

The following post from 2/2003 addressed a fix, which seems to work thus
far:

a.. From: Michael Calabrese <m2calabr ( at ) yahoo ( dot ) com>
b.. To: pgsql-odbc ( at ) postgresql ( dot ) org
c.. Subject: Re: Error when accessing tables with deleted columns
d.. Date: Mon, 3 Feb 2003 14:16:29 -0800 (PST)

----------------------------------------------------------------------------
----

I just wanted people to know if you have deleted a
column in postgres and can not relink the tables in MS
Access, the current solution is to
dump the database and reload it.

I was using 7.2.5 version of the odbc driver and
tested the CVS that Dave kindly arranged for me. If
someone would like me to test a later CVS please just
email me with the location of a compiled version and I
will attempt to recreate my problem.

Thanks for everyones help,
Michael
Thanks,

David P. Lurie