Jeff Johnson wrote on 2013-11-22:
> I have a site that has been working fine for years. All of a sudden one
> file is throwing the above error on one table only. You can view the
> table fine. The problem is on add. There is a stored procedure that
> bumps up the primary key on add. When the stored procedure is called it
> throws an error number 3 File In Use. Here is the stored procedure.
> * Lock until user presses Esc
> SET REPROCESS TO AUTOMATIC
> IF NOT USED('id')
> USE broker!ID IN 0
> ENDIF
> SELECT ID
> **********************
> SET ORDER TO TAG TABLE
> **********************
> SEEK (tcAlias)
> IF FOUND()
> IF RLOCK()
> lnID = ID.nextid
> REPLACE ID.nextid WITH ID.nextid + 1
>
> UNLOCK
> ENDIF
> ENDIF
> SELECT ID
> USE
> SELECT (lnoldarea)
> SET REPROCESS TO lcoldreprocess
> Any ideas?
Jeff,
I suspect it is on the USE command. I have customers get this behavior when
they have aggressive anti-virus or on demand backup tools that will put a
temporary lock on a file that was just updated.
Tracy Pearson
PowerChurch Software
_______________________________________________
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.
