multiple users and forms

[louis-m]

Hi, very new to access and chucked in at the deep end.
we require a database which will be used by multiple users to place orders.
the users are at different locations although they all log on via terminal services so connection issues are minimal.
i understand that we require a fe/be database because of the users.
the users will only work with forms and reports. they should not be allowed to see the other users orders and the form needs to automatically put the users id into the order.
the only way i can see to achieve this is to make a custom form up for each location. would i be right in assuming this?
if so, how would i prevent one location from opening up another locations form? infact, i wouldn't want one location to know that there are other forms for other locations.
any help would be appreciated. thanks

 

[MStef]

Hello louis!

I can offer you this method.
Look at "DemoMultipleUsersA2000.mdb" (attachment).
Open MainForm and try.

 

[louis-m]

thats a nice method but its probably a little bit over the top for what i'm after.
i was thinking more of a backend database with an orders table with multiple frontends, basically all the same apart from a hard coded stamp to say where the order came from and a customized header for each form.
that way, when a new site comes online, it is only just a question of copying a new customized front end (from a master front end) to the sites home folder on the terminal server.
the head office front end will be totally different due to them having to run different reports (totals for all sites etc)
am i thinking along the right lines here?

 

[Rabbie]

Louis-M, your solution will work provided you make sure that the fe is sent to the correct location. You have highlighted a benefit of splitting your Db.

 

[louis-m]

thanks for that. the be will be stored on a share so i can't see there being any problems as the fe's will be stored in individual home shares all pointing to the be share.
btw, i've not tried this yet.... just thinking it through. so i assume that i want a fe masterfile stored in a private file that can be wheeled out as and when required and ammended. once i get each fe customised, should i change it to an mde to further secure it?
ultimately, we could end up with 60+ fe's which are accessed infrequently but this way, i am assured that each site can only access the parts that they need and further security is done by the file system itself.

 

[neileg]

Rather than hard code the location, with 60+ locations you would be better of using the user ID to determine the access. Then all you need to do is maintain the user table and have one FE.

 

[louis-m]

could you explain roughly how to do this? i'm very raw with this at mo and just trying to think my way through it logically prior to attempting it.
the thought of a table with the users stored within it did cross my mind.

 

[neileg]

You can get the current login name using Environ("UserName")

You can use a table to hold the user name and a department or location ID and by using Environ("UserName") as a criterion, identify the ID or IDs they can see. When you record a new order, store the relevant ID with the order details. Any time you want to display the data, use the user name/ID table to restrict the access.

 

[louis-m]

ummm....
i take it, its just a copy and paste into a txtbox using =Environ("UserName")
as the control source, just to see the current username. all i get is #name? returned