G
germaine.oliver
Smart people: I have a split database I have been using for over a
year with no funky issues. We add and delete records every day, so I
have "compact on close" set up on the front end db. Last week, it
started a) creating the db1, db2, etc, and not deleting them and b)
not compacting. db1, db2, etc are all functional databases. My
understanding of the process is this:
1. User closes db
2. Access creates a new db, and compact it, naming it db1, db2,
whatever.
3. Access deletes original, then renames db1 to original file name.
Mine seems to be hanging at step three. I get a new, compacted db, but
it's got a new name (db1, db2, whatever), and my original uncompacted
db is still there.
So, did some testing, found this out:
1) It only occurs on network drives. C: acts normally.
2) It occurs on both back end and front end dbs. So even moduless db's
do this, so it's not a corrupt db issue (I did a decompile, made no
difference, just for the heck of it).
3) I have all permissions on the folder except "full control" and
"special permissions". That is set my out IT folks, and that hasn't
changed. I can add and delete stuff all the time, so I don't think
it's a security thing.
4) I have oodles of space, so it's not the space shortage issue.
Thoughts? I'm stumped. I can't keep creating infinite dbs, and have
the db keep growing, and growing.... I need to compact!
Help!
year with no funky issues. We add and delete records every day, so I
have "compact on close" set up on the front end db. Last week, it
started a) creating the db1, db2, etc, and not deleting them and b)
not compacting. db1, db2, etc are all functional databases. My
understanding of the process is this:
1. User closes db
2. Access creates a new db, and compact it, naming it db1, db2,
whatever.
3. Access deletes original, then renames db1 to original file name.
Mine seems to be hanging at step three. I get a new, compacted db, but
it's got a new name (db1, db2, whatever), and my original uncompacted
db is still there.
So, did some testing, found this out:
1) It only occurs on network drives. C: acts normally.
2) It occurs on both back end and front end dbs. So even moduless db's
do this, so it's not a corrupt db issue (I did a decompile, made no
difference, just for the heck of it).
3) I have all permissions on the folder except "full control" and
"special permissions". That is set my out IT folks, and that hasn't
changed. I can add and delete stuff all the time, so I don't think
it's a security thing.
4) I have oodles of space, so it's not the space shortage issue.
Thoughts? I'm stumped. I can't keep creating infinite dbs, and have
the db keep growing, and growing.... I need to compact!
Help!