Is it like a device timeout error or what? I don't get the err very much. If I let my program go all night long, it usually stops from err 70. :-?
If you had hit the help button on the error message window, you'd have seen this (if you're using QB's IDE):
Quote:An attempt was made to write to a write-protected disk,
a read-only file, or to access a locked file.
Some Windows programs lock a file they are working with - that's probably why you're getting the error... unless you're attempting to write to a read-only file or write protected floppy or something.
but when I hit f1 it sometimes returns nothing but garbled text. I'm not attempting to write/read to any files, so I'm sure that it has something to do with DS4QB or the future timer. I figured it was a dumb question, oh well.
No, it's not a dumb question.
If you press F1 at the error message window, you sometimes see garbled text? That's not good. Sounds like some other part of your program is overwriting memory used by QB.
If I forget to add a NEXT, END SELECT, END IF, etc... it does that. It's a pain to sift through the code and find the error. I guess it's good practice though. :wink: