error 3021 no current record, only sometimes



I have an Access 97 database front end (with some lookup tables there
too) which also has a MS SQL Server 2000 back end, where all the rest
of the larger tables are. I recently had some problems with people
being able to access things, getting ODBC errors when trying to open
tickets. I checked the file DSN advanced configuration and changed it
from named pipes to tcp/ip which is what it should have been in the
first place (I think there was some software pushed through the network
but nobody wants to admit to it). I also updated the MDAC on each
user's PC to the newest from Microsoft's site (2.8, sp1, I believe).
This has fixed the ODBC error on most of the user's computers and they
can all open tickets now, but a few of them are getting 3021 "No
current record" errors. I don't understand why, because everyone is
accessing the same database front and back ends, the same way (on a
network drive) and everyone has the same file dsn configured the same
way and the same version of MDAC. What would account for this, and
more importantly, how can I fix it? I'm not all that familiar with
this ODBC/SQL server stuff but I do what I can with a little direction.
Let me know if any more information is needed. Please reply via the
newsgroup. Thanks for your help.

.



Relevant Pages

  • RE: SQL server Login connection failed sqlstate 28000 sql server e
    ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
    (microsoft.public.sqlserver.odbc)
  • Re: large varchar columns in SQL server
    ... I had users' data stored in a SQL server database that was ... database is gone but we kept the resulting web page. ... Depending on the version of your MDAC driver, ...
    (microsoft.public.inetserver.asp.db)
  • Re: 64 bit MDAC needed
    ... MDB uses Jet Engine, which is 32 bit, and will not have 64 bit version, for sure. ... You may consider to upgrade your *.mdb database to *.accdb, then use MS Access database engine. ... If you can use MySQL, I do not see why you cannot use SQL Server Express. ... I'm in desperate need for 64bit MDAC components. ...
    (microsoft.public.dotnet.general)
  • Re: large varchar columns in SQL server
    ... database, querying the database, or storing the values? ... Aaron Bertrand [SQL Server MVP] wrote: ... can't be sure what version of MDAC they were run under. ... As Bob suggests, it's going to be really hard to tell. ...
    (microsoft.public.inetserver.asp.db)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)