linked dbf tables have "invalid names" after conversion from Access 97 to Access 2000

[David Trebacz]

We're using dbf files to bring data from another application to Access for
detailed analysis and reporting. We have recently upgraded from Access 97 to
Access 2000. Everything seems to have converted fine except linked dbf
tables. The previous linked tables worked fine in Access 97 for several
years.

When you try and open the table Access 2000 reports that :

" is not a valid name. Make sure that it does not include invalid characters
or punctuation and that it is not to long.

Even if we try and relink to the dbf files we get the same error. We have
found that if we move the files to a directory that doesn't contain spaces
in the name -it all works fine. We really don't want to rename the
directory, since it is shared by many applications and will likely break
other things.

 

[John Nurick]

Hi David,

The dbf import routine has a problem with long folder or file names. If
you can't rename the folder, try referring to it by the short name that
Windows has assigned to it (e.g. "C:\Program Files\" is usually
C:\PROGRA~1\).

If you open a command prompt the DIR command will show you the short
names; in Windows XP use DIR /X; other versions may vary.

 

[Brendan Reynolds]

Could you map a network share to the folder and use the UNC name
(\\ServerName\ShareName\FileName.ext) to link the table?

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.