Deploying / installing a new database (2 Viewers)

[gemma-the-husky]

Sorry gemma but I absolutely disagree. Application programmers are not more capable than the RDBMS engine of deleting the correct records. I understand that there are cases where you would not ever want to delete records but would flag them instead but once you decide to delete them, it is far better for the db engine to do this than for you to program it. Not to mention the fact that many databases are shared by different applications. You would then need code in all the fe applications to either prevent deletes or cascade their effects - truly bad business.

i see what you mean, Pat.

I was coming more from the pov, that with cascading deletes permitted, a user could very easily inadvertently delete data that was actually required within the system.

 

[Jeanette Cunningham]

The front end won't compact the backend automatically.

There is a sample database that shows how to write code to compact the backend.
http://www.rogersaccesslibrary.com/forum/topic378.html

Note: you can't compact the backend while any of the front ends are connected to the backend. All users will need to be logged out of the backend so you can compact it.

 

[robsworld78]

I'll save them as querydefs on day if I think its needed, need to see what happens to file size as data is entered, so far so good and its been used a few days.

I was just worried about bloating the file as that appears to affect it. I know the code I have isn't the fastest or most efficient by any means but its not slow, as time goes on I'll be re-writing a lot of it as I know more now. Because I didn't know how to do things as I was building I came up with radical solutions to a lot of things which now I know a better way and will replace, main thing is its working as it should so I feel I've accomplished something.

Thanks for the link with that code, it won't work right now the way I have it setup, when the frontend is open it connected to the backend, can't have it open without a connection. But one day in the near future I will change things so I can incorporate it.

Thanks for all the valuable info from everyone and willingness to help!

 

[Severin]

if you create a shortcut to your file then change the path in properties to path plus a space plus /compact then open with your shortcut when the db is not in use. You can also use a command like /repair and you can combine them!~)

 

[robsworld78]

if you create a shortcut to your file then change the path in properties to path plus a space plus /compact then open with your shortcut when the db is not in use. You can also use a command like /repair and you can combine them!~)

So that shortcut would point to the backend file?

Then when frontend is closed run the shortcut and it did its thing?

 

[Severin]

yes!~)

...Tip: If you have a corrupted database and you can't get in... then use /compile it will often do the trick..

 

[robsworld78]

This saves me a lot of work. Thanks!

 

[Severin]

great!~)

...it's a good trick.. you can also send commands into access this way...

 

[morfusaf]

Nice, thats a good deal!

 

[evanscamman]

Single biggest thing you can do to improve form loading speed:

Change your database to read-only or MDE. Takes the load time from up to several minutes down to seconds.