467,169 Members | 986 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,169 developers. It's quick & easy.

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.

Nov 13 '05 #1
  • viewed: 1743
Share:

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Colin Graham | last post: by
9 posts views Thread by Robert Wing | last post: by
3 posts views Thread by windandwaves | last post: by
5 posts views Thread by prakashwadhwani@gmail.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.