"but I was wondering if it would still be best to split the database into a frontend and backend. "
Absolutely. It's *always* best to do that. For one reason, down the road you will most likely need to be make additions/changes ... and they will have already entered data, so you don't want to have to stop work for some amount of time so you can have the mdb to make those changes. Instead, you just replace the FE with the new version and relink to the BE.
If you are serious about selling a commercial runtime app from a web site, you are absolutely going to need the professional installation package below:
http://www.wise.com/Products.aspx ' Wise, sadly is now owned by Symantec.
http://www.sagekey.com/ The sage key scripts pretty much help you avoid all the issues you have identified. I have two clients the I do some work for ... and both have commercial Access products that they see ... runtime of course. Both have been using the above pair for several years ... with minimal issues.
Also, you will need this:
http://www.microsoft.com/downloads/details.aspx?FamilyId=D9AE78D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en ' Access 2007 Runtime Download - free
see this also:
http://msdn.microsoft.com/en-us/office/bb229700.aspx 'Developer Extensions
mx