We have a possible Problem with the write event.
Using Nt Service 2.1
OI4.12
Server 2000
The client is allowed to attach a different volume to work on different data.
When they did an order, they saved the order, then changed companies.
The order got written in the new Data attached. It also updated the seq key in the new data attached.
They have been using the system like this now for around 4 years, and we have never had this problem.
My thoughts is that there somehow was a delay in writing on the server, which caused this to happen.
Has anyone seen this sort of behaviour before.
If we do a Flush and Garbagecollect before we detach the data will that prevent this from happening?
How do we tell the Service to complete the write before we detach the files?
Any ideas will be appreciated.
Gerry van Niekerk
Csoft
Gerry,
If you are using the NT Service with a ServerOnly REVPARAM setting, it really isn't possible for any such delay in writing. A write is always immediately sent to the server handling that file. A much more likely explaination is that the attach was done first and then the order was entered.
Pat
Pat,
Will check setting I dont think it is set to Server only,
It is impossible to write after attach, As all windows /forms are closed before we attach the new data
Tried it many many times
Thanks,
Gerry
Gerry,
I was speculating that the end user did not correctly recall the actual sequence of events…
Pat
Checked it this morning and ServerOnly=1 wasn't set
Now done and hopefully it will not happen again
Toooooo many things to remember
Gerry