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

[Mark Stewart]

It's good practice to keep your lookup transaction
separate from your primarly transaction.  Use an alias
table using the field from your primary transaction to
kick off a separate read transaction.  Doesn't sound
like that is the case.

Mark Stewart