Well I can't beat that but ...
I also use Access FE & SQL Server BE for several production databases.
The largest of these has a SQL file that after 10 years has reached about 1.6GB.
That's despite it having over 300 tables including one with 1.5 million records.
Mind you I do 'shrink' the datafile in SQL Server at routine intervals - similar to C&R in Access
Although I've been using SQL Server for over 10 years, I'm certainly no expert.
I'd say I just know enough to get by ...
I also use DSN less connections as I find this much easier to understand / work with
When I upsized to SQL server, I lost all table relationships - probably because I did it wrongly.
I have RI set up in SQL server but I do so using PK/FK keys. For example:
I thought triggers were just used to trigger events!
Other points:
1. Changing to SQL Server didn't make connections noticeably faster.
However it did make them MUCH more reliable.
Network drop outs became almost non-existent which was one of the main reasons for upsizing
2. Although I have RI set up in SQL Server, the table links aren't shown in Access. I didn't notice this for some time after upsizing & never bothered to re-create them (there are over 300 tables as I said...). This is a summary of the database statistics ...
3. Shared procedures in SQL Server can be used to do very clever things ... but I've only scratched the surface of their power
4. Make sure you use indexes on frequently searched fields to speed up working with SQL tables
5. Wherever possible, use SQL views rather than Access queries so that the processing is done at the server. This should dramatically speed up many tasks - especially when delaing with large tables
6. Making changes to the structure of a SQL BE file can easily be done using a script file.
I can supply my clients with the script files over the internet or by email for them to implement
Much easier than making equivalent changes in an Access BE
HTH