Continuous form timing issue

[jadixon]

I have a subform that is a continuous form. When the user advances from one record to the next and starts typing, after a second or two the record appears to be committed to the database, and the data that was entered is now highlighted. If they are typing and are not paying attention, it causes them to overwrite what they previously typed in.

Is there a way to either change how long a form waits before it commits the record, or how to stop it from highlighting the data so the user does not clear it by mistake?

 

[TheAceMan1]

How are ya jadixon . . .

There's a great many questions that can be asked before this is resolved. My biggest question is: [blue]Does this occur in a specific field or any field?[/blue]

Now . . . you say:

[blue] . . . the user advances from one record to the next and starts typing, after a second or two the record [purple]appears to be committed[/purple] to the database . . .[/blue]

As far as this is concerned, have the users pay attention to the [blue]Record Selector[/blue] of the record their editing. While their editing, a pencil icon

should show. If the record is truly saved, the icon will disappear!

Also as a quick check, Tools - Options - General Tab - Name AutoCorrect Section. Be sure [blue]Track name AutoCorrect info[/blue] is unchecked.

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997
Also faq181-2886

 

[jadixon]

I have only noticed this with the first field on the form, since that is where the data entry really starts. The Track name AutoCorrect info is turned off, so that is not the problem. I see the little pencil icon but as I am typing it becomes a committed record (arrow icon).

 

[TheAceMan1]

jadixon . . .

If your 1st edit occurs in any other field except the 1st, do you get the same results?

See Ya! . . . . . .

Be sure to see thread181-473997
Also faq181-2886

 

[jadixon]

Well, there is another wrinkle in this timing issue besides the single field one.

The subform is a filtered retrieval, where the user can update existing records or add new ones. If there are no records that meet the criteria, the user starts adding them. After adding the first one, if the data he is typing is alphabetically before the previous one (at least I think that is the criteria), after a few seconds, the record he is attempting to add gets added into the database (before he is ready) then changes the focus from the one he was entering to the one that is now in the position he was adding in before. For example he adds one record, then moves to the next empty spot on the form. After typing a few seconds, that record jumps to become the first record, but now he is typing into the second record on the form, which was the first one he entered.

If there are records already in the table this jumping does not happen.

Where can I change how long the system waits before automatically saving the record? Since we went to Access 2000 I have noticed alot of autofill type stuff that now finishes what I am typing after a few seconds, especially in the VBA editor. Is this really a windows/office thing or is it access?

 

[ProgramError]

Sounds as though user could be tabbing past the last control on the form. If so, check that the cycle properties on the form are set to 'current record'.

As for the VBA thing, I've never found anything in access yet that changes the delay time before the auto fill cancelled.. You will see what I mean if you type s in the VBA editor and string appears to allow you to autofill but disappears after a second or so.

Ian Mayor (UK)
Program Error
If people say I have bad breath, then why do they continue to ask me questions and expect me to answer them?

 

[jadixon]

I think I may have found the culprit. One thing I failed to mention is that this application data (back end) is now in SQL Server, and that is when the record problem started.

I found under options->advanced menu a timeout setting for OLE/DDE and increased it from 30 to 60. Things seemed to have calmed down for those users who changed this setting. If this continues to work well I may try to set this through VBA so when the user enters the system it will change the setting for him.