You can't go to the specific record error

[monkeysee]

This is the message I get, when I am trying to add a new record. This has just occurred after using DB for over 4 yrs. I have compacted and repaired. No help. Any ideas?

 

[missinglinq]

Perhaps you doing things in a different manner than in the past? If, for example, you are entering a new record, and then try to add another new record, or try moving to another record, and a required field on your first record hasn't been filled in, Access will give you this error.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[monkeysee]

I checked for missing info on the last 25 records, but did not find anything. Is there a way Access can find the descrepancy other than just giving an error message?

 

[bratsche]

I get this error sometimes when Access can't figure out what the primary key is on the table I'm trying to update. How it loses that information, I'm not sure but it happens randomly, and I fix the problem by deleting and relinking the table.

 

[RuralGuy]

While viewing your code go to Tools>Options...>General Tab and set it to Break on All Errors. Then when the error occurs view the line where the error is occuring and let us know.

HTH RuralGuy (RG for short) acXP winXP Pro
Please respond to this forum so all may benefit

 

[TheAceMan1]

How are ya monkeysee . . .

In my listing of runtime errors I come up with the following match:

[blue]Error 2105: You can't go to the specified record. You may be at the end of a recordset.[/blue]

This occurs when your at the end of a recordset and attempt to [blue]move next[/blue]. Do you have any such loops where your not checking for EOF!? . . .

See Ya! . . . . . .

Be sure to see FAQ219-2884:

 

[hdog]

I too am having the same problem, error 2015 - Can't go to specified record. I developed the db for a customer over 4 years ago and they have had no problems. Now when I try to add a record via a subform I get the error. This is with the exact same db. I am wondering if an access 2000 service pack release could be causing an issue. I am using 9.0.6926 SP-3. Has anyone seen this before???