psugak
03-20-2006, 10:05 AM
Please help! I have created a sql server 2000 database and added a sql database as an front-end application. Using access as front-end, i can create a new record successfully however, i can not EDIT any fields in the record after i create it. I receive an error indicating that someone else is in the table and i can not edit the information. I know its something with Access because i linked an ASP page to the databse and created a record and edited with no trouble. Do guys know what might be causing th is? I am using windows authentication and the users have adequate permissions to read and write to the database.
Also, issue#2, some users, all have same permissions, can access the queries on the databse and the others are receiving an ODBC connection error. Again, all have same permissions. Please help!
SQL_Hell
03-21-2006, 07:34 AM
Hi
are you using linked tables? if so try and relink them
have you tested the odbc connections?
psugak
03-21-2006, 07:39 AM
The users that have XP operating system can successfully connect to sql server 2000. The users with windows 2000 can not connect. Any advice?
SQL_Hell
03-21-2006, 07:42 AM
are they all in the same domain?
what type of authentication are you using?
have you tested the odbc connections on the offending machines?
psugak
03-21-2006, 10:02 AM
Whenever i create a System DSN or whatever on the offending machine, it still receives the connection error. I am thinking that the sql server drivers on XP and 2000 have to match the version on the actual sql server..... because all of our windows 2000 pcs can not hit the database and have a sql server driver from 2003. The xp machines driver is from 2004 and they can connect fine.
accessIT
03-24-2006, 08:52 PM
Remove the DSN connection is one option. Here is a link to a utility that will remove the DSN ""http://www.mvps.org/access/modules/mdl0064.htm"". This should remove the ODBC issue you are currently having.
SQL_Hell
03-29-2006, 12:33 AM
waht version of MDAC is running on the 2000 machines?
try installing the sql server client connectivity stuff on one of the 2000 machines and re-try