Invalid seek offset 1

[mensudb]

Hi,

I have one more "crazy" situation.
Very often, network administrator closes some free tables, without noticing users or telling them to close applications. As a result,our application gives us an Invalid seek offset error, and the application crushes.
Is there a way to check if indexes are ok, or if reading/writing the table is possible?

Thanks in advance

Mensud

 

[mspratt]

Hi Mensud,

If you can't fire the administrator <g> you will probably have to test for the table being open.

IF !USED("MyTable")
   SELECT 0
   USE MyTable
ENDIF

Regards,

Mike

 

[mensudb]

I wish I could fire him, but maybe the best solution for me is to change the company. Nothing is worth of my nerves.

Anyway, thanks for your help.

 

[GriffMG]

Not always the administrators fault.

Sometimes a back-up program will run a little late and hold files open during the working day - when it's waiting for a tape to be changed or somesuch...

Regards

Griff
Keep [Smile]ing

 

[medic]

I've never heard of any backup program that behaves that way. If there's any, it defeats the purpose of why there is a backup program in the first place (i.e. to protect or secure data). What I know is, backup jobs fail whenever a user fails to close files opened for update. And that's one reason why a thoughtless network admin would force kicking out users or closing files in use by running applications.