Linking FEs to BEs - XP Problem?

[Al Camp]

Since my customer migrated to XP, I've had problems with using the Linked
Table manager in Access 97.
The Client has a network, and I am just a single XP Pro user. Occasionally,
I receive the files from the client to work on.

So, I backup my last copy of the FE (Prog) mdb and BE (Data) mdb to
subdirectories, and install the clients current FE and BE.
Occasionally I need to run/test an "old" backup copy of the FE and an "old"
copy of
the BE.

When I try to link the old FE to the old BE, I get a
"You don't have access to the directory C:\.........\081005Bkup\*.mbd
Contact your adminstrator..."
This occurs after I SelectAll, Prompt for New
Location, and hit the OK button to browse to the BE location.
In my normal "working" directory, where I develop the application, I can use
Link Table Mgr with no problems. This appears to only occur in other
(backup) directories.

I'm not sure if I've got an Linked Table problem, or an XP Shared directory
problem. The directory is "Shared", and I can delete all the linked tables
from the FE, and manually File/Import/LinkTables with no problem.

Any suggestions, or information would be appreciated.

Thanks,
Al Camp

 

[John Mishefske]

Since my customer migrated to XP, I've had problems with using the Linked
Table manager in Access 97.
The Client has a network, and I am just a single XP Pro user. Occasionally,
I receive the files from the client to work on.

So, I backup my last copy of the FE (Prog) mdb and BE (Data) mdb to
subdirectories, and install the clients current FE and BE.
Occasionally I need to run/test an "old" backup copy of the FE and an "old"
copy of
the BE.

When I try to link the old FE to the old BE, I get a
"You don't have access to the directory C:\.........\081005Bkup\*.mbd
Contact your adminstrator..."
This occurs after I SelectAll, Prompt for New
Location, and hit the OK button to browse to the BE location.
In my normal "working" directory, where I develop the application, I can use
Link Table Mgr with no problems. This appears to only occur in other
(backup) directories.

I'm not sure if I've got an Linked Table problem, or an XP Shared directory
problem. The directory is "Shared", and I can delete all the linked tables
from the FE, and manually File/Import/LinkTables with no problem.

Any suggestions, or information would be appreciated.

Access 2000 on XP? Do you have the Compact on Close option checked?

A2000 creates a temp database outside the CurrentProject.Path folder and
then copies it back to that folder when it does a compact. Unfortunately
it then inherits the permission of that user's TEMP folder which is
the last user to use the app.

Try opening up the permissions on your defined TEMP directory - that worked
for me. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;295234

 

[Al Camp]

Access 2000 on XP? Do you have the Compact on Close option checked?

A2000 creates a temp database outside the CurrentProject.Path folder and
then copies it back to that folder when it does a compact. Unfortunately
it then inherits the permission of that user's TEMP folder which is
the last user to use the app.

Try opening up the permissions on your defined TEMP directory - that
worked
for me. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;295234

John,
Thanks for that info. I'll check out your link, and try to get back to you.

Just in case though...

Since my customer migrated to XP, I've had problems with using the Linked
Table manager in Access 97.

We're not using 2000.

What I had to do to allow me to relink (via LinkedTableMgr) an old backup BE
to an old backup FE was to delete all the linked tables from the FE and
relink "manually" through File/ImportData/Link Tables. That worked, and now
I can relink with the LinkedTableManager.

Thanks,
Al Camp

 

[Guest]

Yes, XP has something different about the file open api and
dialogs compared to Windows 98. You sometimes have to
change to the folder first, before trying to open a file, and
sometimes it just doesn't like * when it is expecting a folder.

I always found I could get around the problem by changing
the directory and file types methodically, instead of using
the shortcuts I had become accustomed to in Win 98.

BTW, the one that gave me the most grief was the loss
of ... and .... (dotdotdot and dotdotdotdot) to refer to the
"grandparent directory" and "great grandparent directory"

(david)

 

[Al Camp]

David,
Thanks for the info.

I always found I could get around the problem by changing
the directory and file types methodically, instead of using
the shortcuts I had become accustomed to in Win 98.

Could you explain that a bit further?
Thanks,
Al Camp

 

[Guest]

Could you explain that a bit further?

Not really. When I first moved from Win 98, I used to
get this error all the time. Mostly when typing something
like .. or *.* in a file open dialog. So now I don't type
things like that in a file open dialog.

If I was having your problem, I would change the folder
to the target folder first, (by doing a separate import),
then try to do the link refresh one file at a time.

Doing the link refresh one file at a time is normally faster
anyway, because when you try to link to multiple files, you
have to specify the target file for each link. It is faster to
only select the links for one target file at a time.

But I normally refresh links using custom code.

(david)

 

[Al Camp]

OK, Thanks for that info...
Al Camp

Not really. When I first moved from Win 98, I used to
get this error all the time. Mostly when typing something
like .. or *.* in a file open dialog. So now I don't type
things like that in a file open dialog.

If I was having your problem, I would change the folder
to the target folder first, (by doing a separate import),
then try to do the link refresh one file at a time.

Doing the link refresh one file at a time is normally faster
anyway, because when you try to link to multiple files, you
have to specify the target file for each link. It is faster to
only select the links for one target file at a time.

But I normally refresh links using custom code.

(david)