Database splitting and "no current record" error message

  • Thread starter Thread starter Rebecca
  • Start date Start date
R

Rebecca

I recently split a database to reduce the potential for
network users to modify the data tables. The problem I
have is that I have recieved the error message of "No
current record" when I try to access certain forms, while
other forms still work. All my relationships are still
correct, and all of the linked tables are present. Does
anyone know what could be the problem? Appreciate any
help.
 
Try a refresh of the linked tables. I googled around a bit and saw that as
a recommendation in a couple of places.

Also, for the forms in question....aare there any records in the underlying
recordsource (table or query)?
 
Thanks for the recommendations. I have refreshed/updated
the table links, though I still get the message. I
checked the tables/queries for the ones I received
messages for, and there are records in the recordsource.
The queries that relate to the forms also give me the
error message. All relationships are correct, criteria in
the queries, and the data in the tables. Granted its
only 4 forms out of 20+ that do this, but, of course, they
are important ones.
 
The queries that relate to the forms also give me the error message.

This indicates that the problem is in the queries, not the forms. Can you show us the SQL
statement for one of these queries? Try re-creating the query from scratch. I found one
KB article that might be applicable, but only if you are using linked ODBC tables with an
action query, and you don't have the latest service pack for JET:

ACC2000: "No Current Record" Error with Linked ODBC Tables
http://support.microsoft.com/?id=259873

Have you applied the latest service packs for Office, your operating system, and JET?

Tom
___________________________________


Thanks for the recommendations. I have refreshed/updated
the table links, though I still get the message. I
checked the tables/queries for the ones I received
messages for, and there are records in the recordsource.
The queries that relate to the forms also give me the
error message. All relationships are correct, criteria in
the queries, and the data in the tables. Granted its
only 4 forms out of 20+ that do this, but, of course, they
are important ones.
 
Back
Top