Annoying Invalid path message from Link Specification

[Sambodh]

I have a problem in Access 2007 which looks like a bug to me.

I need to link to an external manufacturer's product catalogue downloaded in
csv format. I create this link using the Link Text Wizard, no problems. First
time I close the database, no error message about the link specification
stored in MSysObjects. I re-open the database, the linked table is there, now
I close the database and I get an Invalid path error box, complaining about
the Database field of the Link Specification. Even though this error message
occurs on closing, it does not affect the linked table in any way on
re-loading. What is going on? I am upgrading an existing product and do not
want this unnecessary error message to come up every time my client closes
the application!

In trying to solve this problem, I tried opening the csv file with Access
2007, thereby creating a database with only one table linked to the csv file,
with the identical entry in MSysObjects. Then I imported all my normal
tables from the production back-end database, and to my great surprise, no
error message now when closing down, no matter how many times I open, close,
etc.. BUT, if I now try to link to this csv table from my front-end accdb, lo
and behold the error comes back again. So it must be related to splitting the
database into front and back ends, which I have to do for this application.

If anyone can help I will be exceedingly grateful. In the meantime, I will
continue my development and inform the client that the error message can be
safely ignored...

 

[Clifford Bass]

Hi,

Do the path to the CSV or the CSV file itself have any apostrophes (')
in their names? For example "C:\Documents and Settings\John\John's
Files\Henry's.csv". If so, remove them. See if that makes a difference.

Clifford Bass

 

[Sambodh]

There are no apostrophes in the path, no special characters at all. Still a
mystery and I reckon it's a bug associated with splitting the database into
front and back ends. I've worked around it by importing the CSV into the
front end, but I'd still like to be able to do it the other way, as it
increases the size of my front end by about 20 Mb...