Slow data update/add in Split DB

[rvanl]

I recently split my 2003 DB into a FE linked to tables in the BE. The
FE is on the local desktop and the BE(w/ short name) is on a shared
server.

When I launch the DB, the form itself displays and populates edit
boxes and dropdowns quickly and populates datafields on multiple
tabs(about 100 fields total, maybe 50 max on the most busy tab) within
a second or two. Navigating from record to record also results in an
almost instant data response

The issue is when we are updating or adding data. After editing or
adding data in any control on the the form, it takes about 3-4 seconds
to update the information and allow movement to the next field.

Any clues what may be causing this behaviour?

R

 

[Danny Seager]

are these 100 fields all in 1 table?

 

[Klatuu]

No data is being updated to the back end when you enter data in a control.
The data is not updated to the back end until you explictly save the record,
navigate to a different record, or close the form.

This means something else is happening. Is this behavior consistent to all
controls on all tabs? What event procedures are you using on the form. It
is not uncommon for events to fire at different times than when you think the
are or in some cases they can be caused to fire multiple times.

Since moving from record to record is fast, that indicates it is not in
saving data to the back end, but something going on in the application that
you are not seeing.

 

[rvanl]

Ah hah. Dave, there's a reason why you're a MVP, eh?

I have a logging function that logs when/where/what/who to another
table for all controls at afterupdate which, as part of the function,
did a form refresh. I'm not 100% sure why I had that bit in place,
but I'm assuming there was probably a valid reason since I try to
avoid refreshes as much as possible.
Rem'ed out that one line and things are working much more
appropriately. Now it's just a matter of figuring what scenario was
not updating things as I wanted and qualify the code.

Thanks,

R

 

[Klatuu]

Glad you found it.
If you are doing an audit log, I would suggest you develop a method that
doesn't go to the database until you update the current record in your form.
You may try reading the info at this site for good ideas:

http://allenbrowne.com/AppAudit.html