foreveryoung
Programmer
We have SQL Server and an application written in Microsoft Access 95. My task was to get the data onto the SQL Server from the Access database, delete the data on the Access database and then link the data from the server into the Access Application.
My theory was to attach the tables when the main menu opened, the user could flick from screen to screen, doing what they had to do. When they closed the main menu however the tables detached themselves.
This worked fine when only one person was using the application. The idea fell apart when two people (person 1 and 2) were using the application at the same time then when someone (person 1) closed the main menu, this detached the tables and left person 2 with no tables and error messages saying it cannot find the relevant tables.
Has anyone else had this problem, or can anyone comment on it. I thought that being multiuser a copy of the database was created on the client PC and any changes were only applicable to that computer. Obviously not. I have linked the tables and am now not deleting them. All works fine.
By the way the idea was chosen so as to force the user to enter their SQL Server authentication logon and password. Only when these credentials were validated against the server would the tables be attached. Has anyone else adopted this method and has it proved problematic? Should I abandon this idea and use the workgroup security? I wouldnt need sql server security then would i???
Thanks
David
My theory was to attach the tables when the main menu opened, the user could flick from screen to screen, doing what they had to do. When they closed the main menu however the tables detached themselves.
This worked fine when only one person was using the application. The idea fell apart when two people (person 1 and 2) were using the application at the same time then when someone (person 1) closed the main menu, this detached the tables and left person 2 with no tables and error messages saying it cannot find the relevant tables.
Has anyone else had this problem, or can anyone comment on it. I thought that being multiuser a copy of the database was created on the client PC and any changes were only applicable to that computer. Obviously not. I have linked the tables and am now not deleting them. All works fine.
By the way the idea was chosen so as to force the user to enter their SQL Server authentication logon and password. Only when these credentials were validated against the server would the tables be attached. Has anyone else adopted this method and has it proved problematic? Should I abandon this idea and use the workgroup security? I wouldnt need sql server security then would i???
Thanks
David
