Should i split the database

[tagteam]

I am designing a database to manage railcars. There are about 4000 railcars and then related records for repairs, upgrades, leasing etc. I have an office with 5 people so. I am wondering if splitting the database is better for security and performance when i am in such a small environment with so few users and records. It seems like splitting it may make it a bit harder to work with and update.
Thanks

[JoeM]

Yes, split the database. It will make it more stable and actually makes it easier to do database updates (you can work on updating the front-end while people are still working in the database).
I do not find it any harder to work in.

[tagteam]

thank you for your response. Are there any downsides you can think of? Would it be an issue if I later decided to upsize it and make it a sql express backend?
Thanks

[JoeM]

Can't think of any downsides. It is actually the recommended way to go.
Some people find the distribution of new front-ends to users to be a little bit of a pain. I just use a batch file which checks to see if they have the most current version of the front-end, and if they don't. downloads the latest copy to their workstation. Works pretty seamlessly.

We have moved split SQL databases before to SQL backends without issues (just a little bit of work, but no more so in converting an un-split Access database).

[tagteam]

thank you for the support. I feel confident in using this layout to plan my database.