Since the first version of Microsoft Access was released in 1992, developers have been using it as a rapid development platform for database applications. However, almost as long as this has been going on, some of these developers have found that their applications often hit the limits of what Access can efficiently manage. Too many users attempting to use the same database at once, too much data stored in the database, and other problems are common to Access applications. As a result, many applications have needed to be migrated to more robust, client/server database systems. In the early days of Access development, this meant having to manually re-create the database on an RDBMS, such as SQL Server, and then revamping the user interface to handle the new backend. Creating a duplicate of the original Access database from scratch on another system was a very difficult task that was prone to error. Tables could be missed, field translations could be done incorrectly, stored procedures and views could have errors, and generally the application might not function properly. There was also no easy way to migrate the data that was contained in these databases. Often, the databases being migrated contained a large amount of data that users wanted to retain in order to have an historical record.
KeywordsAccess Database Error Message Enterprise Manager Validation Rule Parent Table
Unable to display preview. Download preview PDF.