Database Split

[mjn015]

I recently split my database and also used Bob Larson's Autoupdating tool. Everything appeared to be working fine until a few users were unable to access the db. I later found out that because they are at a different site, they don't map to the server that houses the database BE. However, even if they manually map to the correct server, they are unable to bring up the db Form. They get an error stating the BE "...is not a valid path". My questions are:

1) If I were to copy all the files (the Master FE, BE, and MDE) to a public folder that ALL users have access to, will everyone be able to bring up the database Form?

2) How would this affect what was already set up when I ran Bob Larson's utility (or even the splitting and MDE creation)?

3) Is there a way to "Undo" what was previously "Done" to this database (ie: Splitting, Larson Utility, MDE creation) in order to correct the issue, or do I need to start from scratch and split the database while it's on a Public drive.

I hope this makes sense. Thanks in advance for your help.

Michael

 

[boblarson]

Is your network server even available via the WAN? You say that they can navigate to it, but they can't link to it. Do they have appropriate permissions on the server?

 

[mjn015]

Yes, the server is available on the WAN. When the users login scripts run, they get their I: drive mapped to a "Manhattan" server, but all the database files are on a "Bronx" server and that's where they were when I did the splitting, etc.

When I visited a user in Manhattan, I disconnected them from their current I: drive and mapped I: to the server that houses the database. They have permissions to the directory, but they cannot bring up the form when they double click the MDE file I provided them on their desktop. Even if I try the MDE file that's on the server itself OR the Master MDB file on the server itself, the user still gets the message that the "...AUDIT_be.mdb is not a valid path"

 

[boblarson]

1. Don't use drive letter mapping - use UNC (universal naming convention) for the mapping.

2. The MDE file mapping would be based on what the MDB was and therefore UNC really is the only way to specifically specify which server, etc.

To do that here's a couple of screenshots to show you one way to do it:

In your MDB front end file delete the current linked tables and relink using this -

 

[mjn015]

I'm sorry Bob, but how do you delete the current linked tables or can I just follow your steps?

 

[boblarson]

Just use the Linked Table Manager to set them in my instructions.

 

[mjn015]

Pardon my ignorance, but if I do as you say, wouldn't that be deleting each table? And don't those tables contain all my data?

 

[mjn015]

Sorry Bob, I looked at the Help file, and it says I'd just be deleting the link. I get worried when I see the word Delete!

 

[mjn015]

OK, I deleted the links and reestablished them using the UNC path. Do I now have to create a new MDE file and distribute that to my users?

 

[boblarson]

Do I now have to create a new MDE file and distribute that to my users?

Yes, that is what you need to do.

 

[mjn015]

Bob,
Thanks for your help. Your instructions worked perfectly!