Record navigation problem in subform

  • Thread starter Thread starter John
  • Start date Start date
J

John

I have developed a database in Access2000 with a form
and a subform that has the same functionality as the orders
form in the NorthWind .MDB In other words a main form
with a subform in datasheet mode.I developed the database
on my pc at home to be able to use on the network at the office
which uses Access2002. No problem so far.Every thing seems to work fine.

My Problem is as follows. On the Access2000 system at home
The form and subform operate as expected.
On the Access2002 system, when I place the cursor in a filed for a
new record in the subform(datasheet), before I can do anything,
a new record is automatically created AND saved, the new record indicator(*)
moves to the next line. Even without adding any data, if I move
the cursor out of the new rec to an existing record the new/blank record
remains.
If I keep moving the cursor from one new record to another WITHOUT
adding any data, new blank records keep getting created.
This deosn't happen on the Access2000 system.

Am I doing soemthing wrong or are there incompatibilities with the
2 versions.
 
John, this should not happen in A2002. Is there any code that could be
causing the effect you see?

Look for anything in the Current event of the form, or in the Enter or Got
Focus events of the control.
 
Thanks for the reply Allen,
My concern & quandy is that there are No events that fire
for either the main or sub form untill data is entered...
i.e. On the SubForm I have several Afterupdate events for
individual fields, that do calculations on the field.
But these only fire AFTER data is entered and the cursor
moves out of the field. The calculatuion populates another field on the same
subFrm.
Other than that I have no other Events firing.
As I mentioned It is working exactly as I want on my HomePC
but on a the Office system with the SAME Identical forms that I imported
from my HomePC I have the described problem.
I am at a loss as to how to resolve this....
Again thanks for your input!
 
John, there must be some event or code or behavior that is dirtying the new
record in the subform.

Could you open the subform table in design view and set the Required
property for one of the fields to Yes? This would stop it from saving the
new blank record. You may then be able to discover what code is running at
the point when the attempted save fails.
 
Back
Top