to split or not to split my db?

[RLehrbass]

My Db is designed to be used on only one stand alone pc.
Should I split it anyway? is it better to have a front end and back end in case it ever needs to be applied to a network or even for better security?

[June7]

Access files can become corrupted, especially if there is a lot of customization and especially during early development when design can undergo significant changes. However, I have not had this happen to me in quite some time now. Splitting can reduce chance of data corruption beyond the point of recovery. Maybe good enough to do regular backups instead. I have only one large multi-user database and that is definitely split. All other dbs I have are not split. I have never lost data.

[CJ_London]

All other dbs I have are not split. I have never lost data.

I have - and there are plenty of threads on this and other forums where they have as well.

Having said that - I just think it is cleaner to keep them separate, for the couple of minutes it takes to split it you have added a level of safety to your data.

[pbaldy]

The only db I have that isn't split is a little PC inventory app that I'm the only user of. I'd split yours, if for no other reason than when you want to update forms, reports, etc you can do it on a development front end and then simply replace the front end on the stand alone computer when you're ready. If you have an unsplit db, you have to take it out of production to work on it, or copy all the data into a new version.

[pbaldy]

I have - and there are plenty of threads on this and other forums where they have as well.

Last year I helped a new client split a multi-user app they'd had running for a while (I was called in to add some functionality). He had mentioned that it seemed to corrupt every couple of weeks and they had to go to a backup, I suggested that splitting it may solve that. It hasn't corrupted since.

[RLehrbass]

Ok, I chose to split my DB.

[pbaldy]

I think you'll be happier in the long run.