Unanswered: Access2003: Files, Networking, SQL, vista and Backups
I'm still working on the database ATM and these aren't my immediate concerns, but I figured that I might as well ask now while its still early on.
1. Does access ever store the data, forms, etc into separate files or are they all just lumped together into a single mdb file? (short of manually exporting each table contents into, say excel) When creating backups, which files should be taken note of?
2. What is the general networking setup used for access-based databases? what defines the client and the server? In conjunction with question 1, what files will I eventually copy into client workstations, or do they simply use the forms over the network?
3. Is access compatible with other database servers? Can it be used to create forms, queries and something like a front end for data tables hosted on something like MySql?
4. Does Vista have any problems with Access 2003 files?
1. One MDB, unless you split the database, then there's two. A front end (FE) that has all the forms, queries, reports and code and a back end (BE) that has all the table definitions and data. Backup all MDB files.
2. The BE must stay on the server. The FE can stay on the server or be put on each client machine. I tend (now, thanks to Paul ) to have the FE on the server as well and use a VBS file (each client has a shortcut to this) to copy and launch each user's instance. I'm pretty sure the details of this is in the Code Bank. I think he calls it something to do with cloning, which is just a fancy word for copying.
3. YES! MySQL and MS SQL Server are often used as a BE to Access DBs.
4. No. Vista has lots of problems with compatibility, but it runs Access 2003 fine