On 02/06/2017 11:26, Michael Madigan wrote:
<snip>
2. The line code that triggers this
set century on
replace gemdebto.dmmemo with
gemdebto.dmmemo+chr(13)+chr(13)+chr(10)+"Notes:"+dtoc(date())+' '+time()+'
'+"Computer:"+padr(memuser,15,' ')+' '+memnotes
flush
Why no rlock() before the replace? In a multi-user setup using fpw2.6
you should be locking before the replace, then unlock after.
if rlock()
replace debt.lastworked with date(), debt.nxt_con_dt with date()+7
flush
endif
I know I can do that in one line with one replace command, and one flush.
You should have an UNLOCK after the replace then you can flush or not.
I have found that if you move off the record after the replace (go top
say) then it flushes anyway.
HTH
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR.
Tel:0161 831 3700
Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
