problem with 'lookup on' and writing to a SQLserver table

[Lloyd, Gavin]

The autocommit would release the lock but what worries me is doing the
write in the process procedure.  If you are updating a record based on
the logic in the screen then you cannot guarantee the update will be
completed until the update procedure.  So if this doesn't get done will
the SQLserver table be out of synch?

If the updates are related you may be able to change the lookup file to
secondary and your field changes to the process procedure and the update
should sort itself out.  If it's all procedure code you may be able to
use a designer file.

If I have misunderstood then I can only apologise in advance but I had 5
minutes and thought I would try and help for a change but as usual MY
suggestion sounds a lot more complicated than the original question.

Regards,
Gavin.


-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of
brian_matthewsbrian matthews
Sent: 20 April 2004 16:06
To: powerh-l@lists.sowder.com
Subject: problem with 'lookup on' and writing to a SQLserver table


I have never used this list before so am not completely sure what to
expect 
so here goes : I am trying to write to a SQLserver table from a field 
process procedure but the row is blocked if a 'lookup on' is also
present on 
the field, can anyone explain this, or offer a wokaround ?

P.S we are from RMS and trying out SQLserver

_________________________________________________________________
Express yourself with cool new emoticons
http://www.msn.co.uk/specials/myemo