Access 2007 - accdb; options in setting up a reliable multi-user environment across multiple servers? -
I'm having trouble sorting all information / different options in connection with Access 2007 used in a multi-user environment Here's a brief description of my current situation: "Business LAN" on the job that I can log on and can use to configure two other servers through remote desktop. Trade lanes are strictly controlled by our IT department and no one is permitted to install any software or drivers without their consent. Although I have administrative privileges on both servers
The two servers I log on to use to RD are essentially used for the same task, Used for monitoring and controlling the lines. Each server runs a separate program to complete this task, but both programs use SQL Server as back end.
I have combine with the relative information by adding two entry databases (one on each server because they are currently behind separate firewalls) to ask information from the backend of the SQL side of these accesses, in which I have the tables Has compiled in. My program is still in the debug stage to add more details to the data that is collecting the program but ultimately this information can be accessed by regional techniques / maintenance so that their work is easy to maintain on the basis of maintenance staff repairs But I can add even more information .... After all, I have prepared a report which can be run by the Manager / Engineers who are in their area Are looking for the perfect position.
Both are being used to divide the DB so that the back end is different from the forms, questions etc. ... I use the ODBC data source to import the link to SQL. I am using VBA for user authentication, user logging record updates and user / group access control. Everything works the way I intend, except for the fact that which logs on to the server, it will try to run a copy of the front-end. For example, I had a co-worker log on the server via RD to check the program and I logged on from my desk. After entering, I could open those forms. Access was already running. Without being able to establish entry at each person's workstation locally (or even runtime, due to IT restrictions), I'm not sure what the approach is to solve it < P> Additional information, one of the server 1 servers is considered "master server" in which many client stations communicate with "slave server" all. The only way to use the folder on the theater server is log on to the client station and RD runs
Server 2 This server is considered "historian", it communicates with a terminal server in which users Are logged on using the RD and Run applications, which use the SQL backend present on the historian. I am able to install stocks so that some folders appear on the historian from the terminal server.
Can anyone tell me what is my best option?
Thanks in advance
CTN
This is really crazy It is difficult to do your job well, as some IT departments do in every possible way.
You notify users entering through Terminal Server. If so, maybe you can store front end in their terminal server logon's user profile? It assumes that they are not just using the two default admin optimal terminal server logon, of course.
The second thing that is not clear to me is why you need a back end in Access / Jet / AC - why not only link to the SDI server via ODBC and use that data directly. is done? In the same scenario, the only reason for an independent Jet / ACE file with Data Tables is that if you have data stored for your Access app that is not stored in SQL Server. You may also have floating tables (eg, for preparing complex reports, etc.), but they should be on a per-user basis in a database of databases, not shared back over
Comments
Post a Comment