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

Make table query in split database

100+
P: 374
Hi all,

I am working my way through the microsoft tutorial for creating a pareto chart within access.

I am looking to split my database in the near future for multiple user over a network and converint to mde format so changes can not be made to the design.

During the tutorial one aspect is to create a query that performs a make table.

Now, if I split my database will this make query store the table purely on the front end? As I assume if I have multiple users creating graphs there will be a conflict with names of the tables. However if this is kept purely on the front end then it should run pretty ok?

Another consideration is I have read that it can speed up your file if you keep static tables (or very very rarely updated) on your front end and keep the tables that are updated constant on the back end. How do I go about actually picking which should go to the back and which to the front as ther database splitter if i remember correctly just splits all the tables currently within the mdb.

Thanks for any help,

Chris
Jul 21 '10 #1

✓ answered by patjones

One way to handle this (it is not by any means the only way) is to make use of temporary tables that are indeed stored on the front end. You have a query, you make a table based on that query, use the table for whatever your purpose is, then delete the table (or keep the table there until you need to go through this procedure again and simply overwrite it).

As far as there being a conflict with other users, this should not be an issue because each user should have his/her own copy of the front end on their local machine. Don't let all the users open the same copy of the front end on the network drive. It can work, but may lead to problems down the road.

Pat

Share this Question
Share on Google+
3 Replies


patjones
Expert 100+
P: 931
One way to handle this (it is not by any means the only way) is to make use of temporary tables that are indeed stored on the front end. You have a query, you make a table based on that query, use the table for whatever your purpose is, then delete the table (or keep the table there until you need to go through this procedure again and simply overwrite it).

As far as there being a conflict with other users, this should not be an issue because each user should have his/her own copy of the front end on their local machine. Don't let all the users open the same copy of the front end on the network drive. It can work, but may lead to problems down the road.

Pat
Jul 21 '10 #2

100+
P: 374
Thank you for the reply Pat. That is exactly what my plan is at the moment. I assume though when it comes to splitting the database for the first time I should make sure that my temporary table is deleted so that it does not follow to the back end? Then the first time the user runs the front end it will simply make the table within there instead of going to the back end file and creating loads of issues.
Jul 21 '10 #3

patjones
Expert 100+
P: 931
I think that sounds like a good plan.

Another option to look into is whether or not you can base a chart off a query. I never use charts in Access, but if it is possible to use a query as the chart's recordsource then it might present an alternative to creating a table for that specific purpose.

Pat
Jul 21 '10 #4

Post your reply

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