Split or not to split

Today I had a discussion in Microsoft Public Newsgroups about "how to backup a database where tables and forms and everything in one file?" Good answer is "spit your database into Backend (BE, database with tables) and Frontend (FE - database with the rest)". I know the only one reason to have everything in one file - when you develop database in early stage and you are the only user of it. In this case you can make backup any time you like, no problem. But once you gave it to users to enter data - you have to split it. Then I would recommend making a backup every day, at first start, when nobody logged into. In my routine I first make a copy of BE to specified folder, keeping 3 last backup and deleting older (by default) and then I make a compact of BE. I am planning to publish my routine soon, hope it will help somebody also.
Some useful links on splitting databases you can also find at Jeff Conrad site:
Database Splitting Information