Back End UNC Path Problem

[Lorderebus]

Hi!

I've created a small database for the company I work for and it's running ok for most users, but i'm having a problem with one user.

SETUP

Split DB with FE.accde and BE.accdb.
The BE is set on a network and the FE is linked via UNC path.

"Original" FE file is also on the network and I’ve created a small VB.net app to copy the FE to a folder on local computer and open it.

PROBLEM:
All users are able to use the DB as intended, but one user always to relink the tables to the UNC path every time the file is copied.

If I link the “Original” FE on the users machine the other users cease being able to use the db.

I must point out that the user links to this folder with different username of the desktop.

Not quite sure if this is the problem since I have other users that login the same way and they aren't experiencing any problems whatsoever.

Any thoughts on how should I fix this so the user doesn’t have to relink the tables every single time, cause it’s time consuming.

Thanks so much.

 

[apr pillai]

Check with your Network Administrator about access rights of the User with the problems. Send a request to the Network Administrator with one of the User's Network ID and ask him to include the User with problems to the same Group and assign the same permissions to him too.

 

[Mr. B]

When you use the Linked Table Manager to link to the back-end tables, are you using the My Network Places option to get a UNC pathing?

If you us a drive letter to map the path then if a user does not have the same drive letter mapped to the same network location then you can have this type of problem even if the user has all of the correct permissions on the network drive.

 

[Lorderebus]

Thank you in advance for your help guys and sorry about the delay in my reply.

apr_pillai: regarding the groups and the permissions i have serveral other users of the same group with the same permissions that are able to use the DB just this user seems to have problems with it.

Mr_B: i don't use the mapped drives to get to the DB because the users map the drives themselves so chances are that they use several diferent drives letters.

The path i use is something like this "\\Test\whatever\BDI\BDI_backend.accdb"

And i know this isn't a vb.net forum, but like i said before i created a small app to launch the DB that copies the access file to a temp folder, and in this user Directory.Exists Method always returns false, and the folder definitly exists and the user can access it manualy.

Once again thank you guys for your kind help.

 

[Guus2005]

Here's the batch file (slightly modified) i use to circumvent such problems.

@echo off
cls

set APPNAME=BDI

REM Delete current mapping to P:
if exist P: subst P: /D
REM Create new mapping to P:
subst P: "\\Test\whatever\BDI\"

REM Create installation directory if needed
if not exist %temp%\%AppName% md %temp%\%AppName% >NUL

echo .
echo One Moment pleae, files are being copied!
echo ..

REM Copy application to local destination to run faster.
copy "Z:\AllApplications\Launchpad\Your Database\BDI_FE.mdb" %temp%\%AppName% >NUL

REM Start the application
%temp%\%APPNAME%\BDI_FE.mdb

It copies the FE to a temporary (local) directory and the tables in the FE must be linked to BE on the P-drive (subst P: "\\Test\whatever\BDI\Backend").

The P-drive can be anything. It makes testing easier in a different environment. Deploying your FE doesn't require the tables to be linked again. They are always pointing to the P-drive.

HTH

 

[Lorderebus]

Again, sorry about the delay on the replay.

Regarding that suggestion, i don't know if it's possible to implement because there are different groups with different permissions to the drive and PCs.

Some need to type a password and username to log to the drive, some as i said before have to manually map the drive and i think, but I’m not totally sure don't have permissions to map drives. But I’ll see if i can implement what you suggested.