Multiple Users runing Update Queries with random table names

[pazgb]

Hello All,

A little background on what I am trying to do.

I have a shell database that has 1 form and allows users to add/delete/import id numbers into a listbox.

I then need to take these id numbers and run about 12 update queries.

Since multiple users are using this at the same time. How can I run the update queries without have to redo all my update queries? Is there a way to maybe create a random table name for the id numbers and fields I have to update? If so how will the 12 update queries know which random table to update? I've done quite a bit of VBA programming in the past but stuck on this. Would I have to change all my GUI queries into VBA code and use the random table name that was created from the get go?

I hope there is an easier way to do this. My goal is not having to put the front-end db on everyone's computer since we have like 100 people using this tool. If I have to make an update, I dont want to have to update 100 PC's.

Confused and need some help please?
Thanks,
Mike

 

[ChanceD2]

Mike,

Why can't you put the Frontend on the network and have a shortcut on everyone's PC? Then you make only 1 Frontend and therefore only have one to update. Also, I would think about having a 'gateway' app that they are linked to. Then you can point that gateway to multipule apps in the future, without having to add more shortcuts and having more to maintain.

Thoughts?

C-D2

 

[pazgb]

That would not work, If I have 1 front-end all the users would be updating the same table? Need multiple tables so no users overlap others. Any other thoughts?

 

[ProgramError]

Have two back ends. The users back end on their computer to solve the...

If I have 1 front-end all the users would be updating the same table?

problem and the main backend on the network. A frontend on the users computer which can be automatically updated, when the user first starts their application, by downloading it from the network location each time there is an update
or
a link on the users desktop to the frontend on the network.


Ian Mayor (UK)
Program Error
Programming is 1% coding, 50% error checking and 49% sweat as your application bombs out in front of the client.

 

[ChanceD2]

Mike,

Any why can't you have multipule people updating the same table?

This is definately not a limitation of MS Access, it has to be some weird business rule that you have. MS Access can handle like 12 users updating the SAME table at the SAME time.

C-D2

 

[pazgb]

Its not that the users are updating tables, multiple update and delete queries running. I would think that if multiple users click on the macro to run all the queries, that something would bomb.

Thanks

 

[ChanceD2]

The solution that you are looking for is not going to be found using multipule tables. You need to re-work this.

I'm more than happy to try to help, if you want it.

Please let me know.

C-D2

 

[pazgb]

Thanks, Im going to think about this some more and will get back.