|
-
Feb 28th, 2002, 05:38 AM
#1
Thread Starter
Addicted Member
VB's screwing around...
This is REALLY pissing me off, I've been trying to fix it for days.
Based on some unknown factor (I still have absolutely NO clue what causes this), sometimes trying to save data to one of my files will cause the file handle to become invalid. From then on, all file operations on that handle return 'bad file name or number'. I never call the Close statement (I searched through my entire source code and added message boxes to trace every close), and I traced all my values... all the data I'm saving seems to be fine.
Also, this only happens when my app is compiled. If i'm in the IDE, it doesn't happen.
Usually the app is compiled as an ActiveX EXE, and then the client hands it some text and tells the app to save the text. The app then measures the string, saves a 4-byte long containing the length (this is where the error occurs... >_<) and then the string itself.
The error that occurs is... get this, Bad File Name or Number (52).
Anyone have ANY idea what could be causing this?
"1 4m 4 1337 #4xz0r!'
Janus
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|