At 11:05 AM 2/16/2010, Bill Downall wrote:
I am getting an enormous number of Internal Lock Error messages with
one database,
even when there is only one user connected. For example, I can be
editing a form,
and when I go to save it, I get the Internal Lock Error message.
Usually, the form
appears to have saved correctly.
Does anyone have any insights on what commands or settings can
trigger that problem?
Bill,
A routine that DROPs the already defined TEMPORARY TABLE while the
associated form,
report or label is still in use, will generate Internal Lock -ERROR-.
When DROPping the TEMP Table or View, an unexpectedly out of the
WHILE ... ENDWHILE
DECLAREd CURSOR that was not properly DROPed, will also generate such -ERROR-.
You may also observe this particular -ERROR- when performing the
UNLOAD or RELOAD
routines while TEMPORARY TABLE(S) may still exist and not dropped
prior to using
either command. The best practice to avoid such -ERROR- message is to always
DISCONNECT and then CONNECT the database to automatically DROP all
TEMP TABLEs or
VIEWs, if any.
Hope that provide you with some blue's clues ...
Very Best R:egards,
Razzak.
