moving to next line oddity

[Guest]

I have 2 db's that are similar in nature. On each there is a continuous form
that records incoming and outgoing revenue. On DB-1 everytime the row is
completed and the cursor goes to the next line (record) the total in the
footer changes. In DB-2, it is the same type of form but when the cursor
goes to the next line (record) the total in the footer does not change until
the user begins the next record.

I have looked at both and they are the same. Has anyone else come across
this? Anyone have any ideas on what is going on here?

Thanks.

.... John

 

[Linq Adams via AccessMonster.com]

Of course, this is just so much shooting in the dark, but the first thing I
'd check is whether the table in DB-1 has an autonumber while DB-2 doesn't.
If there is an autonumber, the record is actually "begun" when you move to a
new record, before you actually physically enter data. This could possibly
account for the difference in behavior.

I have 2 db's that are similar in nature. On each there is a continuous form
that records incoming and outgoing revenue. On DB-1 everytime the row is
completed and the cursor goes to the next line (record) the total in the
footer changes. In DB-2, it is the same type of form but when the cursor
goes to the next line (record) the total in the footer does not change until
the user begins the next record.

I have looked at both and they are the same. Has anyone else come across
this? Anyone have any ideas on what is going on here?

Thanks.

... John

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

Answers/posts based on Access 2000

Message posted via AccessMonster.com

 

[Guest]

Ling, thanks for the shot in the dark. Both dbs are the same as to property
settings in the forms and the the tables, as for autonumbers. Oh well, no
need to spend any further time on it. There are bigger fish to worry about.
Thanks again.
.... John

 

[Marshall Barton]

Ling, thanks for the shot in the dark. Both dbs are the same as to property
settings in the forms and the the tables, as for autonumbers. Oh well, no
need to spend any further time on it. There are bigger fish to worry about.

In case you're interested, the times I've seen that effect,
it was a timing issue. Access calculates expression values
in a separate, medium priority task. Even when the
calculation has been done, painting the recalculated value
is done in another low priority task.

It it were important, you can usually(?) force it to sync up
by adding some combination of these statements in an
appropriate procedure:

DoEvents
Me.Repaint