When compacting database creates another file

[ramudubai]

Please note I am using Ms access for long time - it was working good- now recently we have upgraded our server and we have transfered all our files - after that when ever the user closes the database- compacting and quit (access 2003) - it creats mb1 and mb2 like that, when I import/copy in the local machine it works perfect- what will be the problem?

Really I am in a deep problem - can any one help me to find a solution - I am not a expert in VB. We have checked the server folder security it is full control

Just wondering how in the local machine it is working good and when in the server it is not working?

Please help

Thanks
Ramu

[abolos]

Please note I am using Ms access for long time - it was working good- now recently we have upgraded our server and we have transfered all our files - after that when ever the user closes the database- compacting and quit (access 2003) - it creats mb1 and mb2 like that, when I import/copy in the local machine it works perfect- what will be the problem?

Really I am in a deep problem - can any one help me to find a solution - I am not a expert in VB. We have checked the server folder security it is full control

Just wondering how in the local machine it is working good and when in the server it is not working?

Please help

Thanks
Ramu

Hi Ramu,

Look, try to remove "Compact on Close" option. This must solve the problem. Then make a schedule for compacting the database manually, maybe every week or two. By the way, how big is your database?

Abolos

[ramudubai]

Thanks for the reply- yes this is one option- but it was working very well - is it because of Jet 4.0 download missing in the server? or any compacting utility is missing in the server?

Any idea

Thanks
Ramu

Hi Ramu,

Look, try to remove "Compact on Close" option. This must solve the problem. Then make a schedule for compacting the database manually, maybe every week or two. By the way, how big is your database?

Abolos

[ramudubai]

Hi

Still problem is not solved, If I removed the compact and close database become double to 16 MB, - is there is any better solution to use compact in the server- Hope I am correct there is compact utility is missing in the server - that is the reason it is working well in my PC and not in the server

Windows server 2003 with service pack 2

Anybody can help me- Please

Thanks for the reply- yes this is one option- but it was working very well - is it because of Jet 4.0 download missing in the server? or any compacting utility is missing in the server?

Any idea

Thanks
Ramu

[Killer42]

Did you sort this one out? It sounds as though one possible cause might be permissions on the server. For example, if the user had permission to create and write to files, but not rename and/or delete them. This sort of weird stuff has happened to me in the past. I even had cases where I could create and write a file, but couldn't see it or read it.

[Schi]

Re:When compacting database creates another file
Issue originally posted by ramudubai

Is there a follow-up to this? The issue is identical to what is happening here; if there is a clue to shorten the discovery-curve, it would be so awesome. Cross fingers . . .

[Ericks]

Re:When compacting database creates another file
Issue originally posted by ramudubai

Is there a follow-up to this? The issue is identical to what is happening here; if there is a clue to shorten the discovery-curve, it would be so awesome. Cross fingers . . .

As I added to a similar request from today, I encounter the same problem when one enters a new record to a (query) sub form by means of a pop up form. The record entered on this popup is not "linked" to anything, gets lost in the database and at that point, when compressing the database it creates a new database called db1, 2 or whatever. Turning off the auto compress function will not create a different database but you still have the problem of lost data.