Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
File in use by another Error Message
Message
De
24/05/1999 17:54:42
 
 
À
24/05/1999 17:41:44
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00222087
Message ID:
00222252
Vues:
18
Hi Nancy,

Jeez, so many things to check!! < g >

1) Well, there is a grid on the form, but the table in question is not bound to it.

2) Haven't tried saving instead of canceling (didn't want to put a lotta records on the tables). I'll check it out.

3) I'm using transactions (and I already know I'm doing it wrong at this point, if I get a chance I'll change it) and so I'm doing a ROLLBACK. I didn't think to try that from the command window after the program suspends with the error. I'll check it out.

4) I'm using default datasessions.

Every little suggestion helps Nancy. Thanks!

Bonnie


>Hi, Bonnie.
>A couple of questions for you.
>
>1. Is the table bound to a grid control?
>2. If you don't cancel the add, but save it instead, can you cause the same error?
>3. In your cancel button, what exactly do you do? A tablerevert, I imagine. If when you get the error, if you do a tablerevert on the table, what happens?
>4. Are you using private or default datasessions?
>
>I don't ever use pessimistic buffering, but since PB sets a lock as soon as editing begins and doesn't release it til the changes are committed or reversed, then I'd look at the point where I think my code is releasing my editing session.
>
>I don't know if that helps any. :-(
>
>>Hi folks! Got another weird one! I'm getting Error #108, "File is in use by another". What the docs tell me is that this error is generated by an attempt to "USE, RENAME or DELETE" a file that is being used by another user on the network. Well, that isn't the case here ... I'm the only one working on this.
>>
>>It's an intermittent error, it seems to be happening on a permanent table, not a cursor, and it's happening when I attempt to INSERT INTO. From the command window I also tried an APPEND and got the same error. But, when I USE'd it to close it and USE'd it again to open it back up, no problem, the error wasn't generated. I'm using Pessimistic Row buffering (so there's no table-locking or file-locking that I'm aware of).
>>
>>It happens when I attempt my "add" code on my form more than a few times (I hit the "Add" button, then "Cancel" it and do this a few times and then the error finally fires).
>>
>>Any ideas?
>>
>>TIA,
>>Bonnie
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform