On updating the application:

http://www.microsoft-accesssolutions.co.uk/split_a_database.htm

This article scares me:

http://www.buygold.net/v07n01/v07n01.html


>Hey,
>
>I need to do some mods to someone's Access application (all data AND programs are in the .MDB file). The coding is not a problem, but I'm more concerned with finding a good tutorial on best practices that might answer some of these questions:
>
>1) How do Access devs usually deploy new code to an existing production application? Is there some easy way to export code from a test .MDB and import it to a production .MDB?
>
>2) I'm assuming that usage of COM objects from inside Access VBA code is possible? Any gotchas related to using VFP COM objects if necessary?
>
>3) Best practices on error-handling -- global handler vs just checking return values of SQL commands, etc?
>
>4) Other than QODBC and nSoftware's iBiz QuickBooks Connector (formerly AcctSync), what tools have you used to integrate Access with QuickBooks Pro 2003 or higher?
>
>5) Good tech support sites for asking these kind of questions?
>
>6) If an Access application is developed using Access 2000 and then you open the .MDB with Access 2003, what kind of problems can be expected? What if you make changes to the tables or code in 2003 -- does it ruin backward compatibility?
>
>Any suggestions, answers or links appreciated.