By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,894 Members | 2,185 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,894 IT Pros & Developers. It's quick & easy.

Problem resulting after splitting a database

P: 4
Hi

When I split my database into a Backend and a Frontend, a couple of strange things happened.

1.) When I run my queries, multiple copies of the same record are displayed (this is wrong, we should only be displaying each record once. They only displayed once before I split the database).

2.) When looking at those queries in Design View, the field names have a prefix such as Expr1, Expr2, Expr3...

Please help!
Giff
Jan 8 '08 #1
Share this Question
Share on Google+
2 Replies


jaxjagfan
Expert 100+
P: 254
Hi

When I split my database into a Backend and a Frontend, a couple of strange things happened.

1.) When I run my queries, multiple copies of the same record are displayed (this is wrong, we should only be displaying each record once. They only displayed once before I split the database).

2.) When looking at those queries in Design View, the field names have a prefix such as Expr1, Expr2, Expr3...

Please help!
Giff
Do you still have a good copy of the database? Make a copy as a BackUp.
If so this is easy.
Put a backend copy on the network or your intended destination. Put a frontend copy on the the network or your intended destination.

Open the frontend and delete all tables that will exist in the backend. Link the tables (all or the ones you deleted if not all) from the backend.
When linking in a multi-user environment make sure to use the UNC path (\\server\folder\mydb.mdb) vice (F:\folder\mydb.mdb) in the event all users mappings arent the same.

The frontend copy should work like it did before you split it out. (Unless you have custom coding that prevents this)

Always backup your mdb's or any projects before attempting changes.
Jan 8 '08 #2

P: 4
Hi

Thanks very much for your response! I do have a backup of the database (actually many backups).

One thing you mentioned I'm a little confused about: "When linking in a multi-user environment make sure to use the UNC path (\\server\folder\mydb.mdb) vice (F:\folder\mydb.mdb) in the event all users mappings arent the same."

I'm slightly confused about how to specify the UNC path versus the usual F:\folder\mydb.mdb.

Do you have any tips about the best way to deliver the front end copies? Most of the people are in my building, but one person is in another and in another organization?

Thanks so much!!!!
Giff


Do you still have a good copy of the database? Make a copy as a BackUp.
If so this is easy.
Put a backend copy on the network or your intended destination. Put a frontend copy on the the network or your intended destination.

Open the frontend and delete all tables that will exist in the backend. Link the tables (all or the ones you deleted if not all) from the backend.
When linking in a multi-user environment make sure to use the UNC path (\\server\folder\mydb.mdb) vice (F:\folder\mydb.mdb) in the event all users mappings arent the same.

The frontend copy should work like it did before you split it out. (Unless you have custom coding that prevents this)

Always backup your mdb's or any projects before attempting changes.
Jan 20 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.