weird write conflict issue

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hi All

Arrrrrrg! Can anyone help me get rid of the write conflict? I cannot figure
out why it's occuring. Senario is as follows. (This all worked fine on the
old version with only one date field)

Database is not SQL but uses linked tables on local machine

Form A has two date fields that if clicked load up Form B with the calendar
control
The date is then chosen and this value is placed in the start or enddate
field on Form A easy!

For troubleshooting I have used to different calendar forms as originaly the
control source swapped
depending on which field had fired off the load event (but it makes no
difference).

I KEPT getting a write conflict after Form B had closed when inputing the
second date (No matter whether or not start or enddate was clicked first)

This was fixed by forcing a requery and refresh of Form A in the close event
of Form B

But now if I try to edit another txtfield on Form A I get a write
conflict.....however it seems not to occur if I wait a while before doing
any edits <this should give a clue. The other odd thing is that if I say
drop the changes it implements them anyhow?!

Any help much appreciated..the project has to be installed tommorow!

Thanks
 
Suggestions:

1. Leave Form B unbound.
If there are any memo fields in Form A's table, the write conflict will
occur even if the forms are not both dirty at once. After selecting the date
in unbound Form B, you can update the value on the original bound Form A
with:
Forms![Form A].[SomeContorl] = ...

2. Make sure you have SP8 for JET 4.
Right-click msjet40.dll (typically in windows\system32) and check the
version. If less than 4.0.8015.0, go to http://support.microsoft.com
 
Thanks Allen

I am running jet8. Added a - Forms![FormA].Refresh - to the close event of
Form B and that seems to have fixed it but I will unbind Form B as you
suggested as all other info data such as name etc. can be pulled on to the
Calendar form (Form B) in code anyway.

Form A does have a memo field but I am still slightly in the dark as to why
this never occurred before.




Allen Browne said:
Suggestions:

1. Leave Form B unbound.
If there are any memo fields in Form A's table, the write conflict will
occur even if the forms are not both dirty at once. After selecting the date
in unbound Form B, you can update the value on the original bound Form A
with:
Forms![Form A].[SomeContorl] = ...

2. Make sure you have SP8 for JET 4.
Right-click msjet40.dll (typically in windows\system32) and check the
version. If less than 4.0.8015.0, go to http://support.microsoft.com

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

John said:
Hi All

Arrrrrrg! Can anyone help me get rid of the write conflict? I cannot figure
out why it's occuring. Senario is as follows. (This all worked fine on the
old version with only one date field)

Database is not SQL but uses linked tables on local machine

Form A has two date fields that if clicked load up Form B with the calendar
control
The date is then chosen and this value is placed in the start or enddate
field on Form A easy!

For troubleshooting I have used to different calendar forms as originaly the
control source swapped
depending on which field had fired off the load event (but it makes no
difference).

I KEPT getting a write conflict after Form B had closed when inputing the
second date (No matter whether or not start or enddate was clicked first)

This was fixed by forcing a requery and refresh of Form A in the close event
of Form B

But now if I try to edit another txtfield on Form A I get a write
conflict.....however it seems not to occur if I wait a while before doing
any edits <this should give a clue. The other odd thing is that if I say
drop the changes it implements them anyhow?!

Any help much appreciated..the project has to be installed tommorow!

Thanks
Click to expand...
Click to expand...
 
Back
Top