G
Guest
Hello All,
I've been experiencing db corruption lately, it looks like when i make a
change to a module. I'm running Access 2002 and the db is 2000. I seem to be
able to recover if I replace a module with an older version (but the changes
are still present!?!)
I've seen the suggestions to decompile at first sign of corruption, but do I
need to "RECOMPILE" it once I have decompiled? Does anyone know what this is
doing, is it putting the modules down at a lower version?
I have also added a read-only user (have got 10 full-data users sharing on
LAN) over a WAN recently. Splitting the db sounds a little complex. Is it
inevitable?
Thanks for any insight anyone can share with me!
I've been experiencing db corruption lately, it looks like when i make a
change to a module. I'm running Access 2002 and the db is 2000. I seem to be
able to recover if I replace a module with an older version (but the changes
are still present!?!)
I've seen the suggestions to decompile at first sign of corruption, but do I
need to "RECOMPILE" it once I have decompiled? Does anyone know what this is
doing, is it putting the modules down at a lower version?
I have also added a read-only user (have got 10 full-data users sharing on
LAN) over a WAN recently. Splitting the db sounds a little complex. Is it
inevitable?
Thanks for any insight anyone can share with me!