Odd... Anyone seen this?

[Tango]

I have a simple form based on a one-to-one query on two tables. For some odd reason it suddenly started acting "strangely" and I have not been able to nail down why.

The first field on the form is automatically selected (normal).

When the form is open. The problem is that if you attempt to edit the value of that field it beeps at you (not normal).

If the user selects the 2nd field on the form and then goes back to the first field they can edit the first fields values without any beeping. Both the 1st and 2nd fields are from the same table.

-------
The form is setup to allow additions or edits of values as is the query. Not sure what's going on. Anyone seen this?



edit---- The form does not use subforms of any kind.

 

[mdlueck]

Do you have any VBA on this Form? If so, set some break points to see what events are getting fired.

Try making a backup copy of the database and decompile it:

NT Command Script and Documented Steps to Decompile / Compact / Compile an Access DB
http://www.access-programmers.co.uk/forums/showthread.php?t=219948

 

[Tango]

No VBA, on this form. I will try the decompile route.

 

[Tango]

Had to edit the script to make it reflect the office 2010 folder location but otherwise it worked great. Unfortunetly it did not fix the problem though. Any other ideas?

 

[Tango]

For the record, I am still having this problem. Anyone have ideas?

 

[mdlueck]

For the record, I am still having this problem. Anyone have ideas?

Since you said...

No VBA, on this form.

I have no ideas. If the Form does not have ANY VBA code on it, then the form should operate with default behavior, apart from preference changes you have specified. I could not begin envisioning what default preferences could possibly be messed with to cause the unexpected operations you originally described.

 

[Tango]

Could it be something odd from the Access 2007 - Access 2010 conversion?

 

[mdlueck]

It works correctly in A2007, you opened the working DB file with A2010 and there it is behaving differently?

 

[Tango]

Oddly enough it worked under 2010 and 2007 until eventually I started getting "unrecognized database type" when trying to open it under 2007. I *noticed* the error in question roughly about that time. Unfortunetly I can't say for sure when it started.

I keep a backup of every version of my database for the last 4 years. Going back to old versions that I know worked before under 2007, the problem is there. So in short, even in old untouched versions written under 2007 the problem exists now (opened with 2010) while it did not exist the last time that front end was edited.