Could someone tell me what would be causes for a " DEVICE I/O Error" to appear?
I have a file that was shared and protected on a server.
It was suspected that someone went into the unpassworded VBA editor and wiped out the sheets from the workbook- leaving only the "shell" of the file behind.
Once done, you could not even "insert a new sheet" --
Now that the damage is done --- when you go to open the file - you get a simple: VBA Dialog Box which says: Device I/O Error
Once you say: OK - then the file finishes opening - and it just looks like an empty shell.
File name is at the top - but no sheets are present any longer.
All options - such as SAVE AS and INSERT sheet are grayed out and inaccessible....
Luckily, I had a back up - but with the investigation - I need more info!
I'm going to be meeting with our IT group to discuss the entire hacker situation today - and want more info on what would generate this error - other than a hacker getting into the file and destroying it.
Or is it plain and simple:
This error was generated (BECAUSE) someone accessed the VBA area and wiped out the guts of the file?
If this is the case - great -- if not -- then I need more info --
Thanks!
Need info ASAP --
Thanks
Chris
I have a file that was shared and protected on a server.
It was suspected that someone went into the unpassworded VBA editor and wiped out the sheets from the workbook- leaving only the "shell" of the file behind.
Once done, you could not even "insert a new sheet" --
Now that the damage is done --- when you go to open the file - you get a simple: VBA Dialog Box which says: Device I/O Error
Once you say: OK - then the file finishes opening - and it just looks like an empty shell.
File name is at the top - but no sheets are present any longer.
All options - such as SAVE AS and INSERT sheet are grayed out and inaccessible....
Luckily, I had a back up - but with the investigation - I need more info!
I'm going to be meeting with our IT group to discuss the entire hacker situation today - and want more info on what would generate this error - other than a hacker getting into the file and destroying it.
Or is it plain and simple:
This error was generated (BECAUSE) someone accessed the VBA area and wiped out the guts of the file?
If this is the case - great -- if not -- then I need more info --
Thanks!
Need info ASAP --
Thanks
Chris