Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"record jump" when inserting a new record! help!

Status
Not open for further replies.

gacaccia

Technical User
May 15, 2002
258
US
i had an access 2000 mdb project that i was linking to tables in a sql server 2000 db. i ran into an issue where access couldn't support some of the queries i needed to run, so i decided to switch to an adp project and use sprocs instead.

i imported my existing forms from the mdb project into the adp project. here's where it gets strange. on one of my forms, which is not using sprocs (data source set to table name), when i insert a new record, i can enter text in the first textbox (which triggers a "beforeInsert" event). but, the moment i change focus to another textbox and type the first letter of input, the form navigates to a prior record and records the keystroke in the textbox for that record!?

this form was imported unmodified from the mdb project. the problem does not occur in the mdb project. the form has an event for "onOpen" and "beforeInsert" only. any thoughts on why this is happening?

thanks,

glenn
 
additional info. it appears to be related to forms that display child records. any form i have that opens up a table of parent records does not have the above problem. however, if i have a form of parent records and i click a button that displays a form of child records, that form will have the problem.

my general approach with parent/child form connections is to pass the primary key value of the parent record using the args parameter. then, i use the "beforeInsert" event on the child record form to update the foreign key value of the child record.

thoughts on why this causing the record jumping?
 
well, it looks like the final solution was to upgrade to office 2003. appears that the bad behavior was a defect/compatibility problem between access 2000 ADP and sql server 2000. after upgrading to access 2003, problem went away.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top