| BillieGoat 2005-04-06, 8:05 pm |
| Thanks, I'll take a look at these. It seems that is what is happening. It does
seem to be a timing issue since it only happens sometimes. Some days more than
others and on one PC over the other but it does happen on all the PCs. I
have made a
couple changes since I posted so I'm waiting to see if these help.
I've checked out the corruption but I really don't think so since it ran
fine with
the 97 data. Of course at first I thought it was that.
One benifit is that I've learned numerous ways to speed things up for the
client.
I'll post what I find so that it may help someone else with this issue.
Thanks
Billie Cornell
"Ken Snell [MVP]" wrote:
> I have gotten this error when using a subform and running code in the
> subform and the main form at the same time. It can be a timing issue for the
> code. What happened for me is that the person was editing data in the
> subform record, then clicked directly onto the main form onto a command
> button that updated the data. Because of a short timing issue, the main form
> tried to save the data while the subform was still "dirty" and hadn't saved
> its data yet.
>
> Here is info from a post I did back in September 2003:
> ----
> This error can occur in many ways (see numerous KB articles about it), but
> the first place to look is for situations where the user can begin editing a
> record in a subform (makes it dirty), then clicks onto another part of the
> form (another subform, or the main form) and causes some code to run on that
> new area of the form. The initial subform is NOT written to its recordsource
> at that time; the subform is still dirty. If your other code is trying to
> edit the same record/table info, you can get this error.
>
> I have overcome this problem on some forms by forcing the subform to save
> its current record in the code that runs on the other part of the form.
>
> It also can be a sign of corruption.
>
> See this URL for some KB articles (watch for line-wrapping, as the URL is
> one line):
> http://support.microsoft.com/search...
Jet+data
base+engine+stopped+
the+process+because&KeywordType=PHRASE&maxResults=150&Titles=false& numDays=
>
> ----
>
> Take a look at your setup and see if it's possible that this error is
> resulting from such a conflict in your code. The fact that you see it on a
> network but not on your local setup is symptomatic of this problem.
>
> If this is the problem, you may need to reprogram the form so that the code
> conflict doesn't occur (cannot click on a button to cause more code to run
> until the one is done), to force the main form's code to finish the
> subform's code by forcing it to save the record in the subform before the
> main form continues, or to put a delay in the main form's code of a few
> seconds or so to allow the subform to finish its updating.
> --
>
> Ken Snell
> <MS ACCESS MVP>
>
>
>
>
> "BillieGoat" < BillieGoat@discussio
ns.microsoft.com> wrote in message
> news:E31C86BF-4AE3-477D-B478- 70BBF33C204A@microso
ft.com...
>
>
>
|