![]() ![]() The client computer should be able to directly access a local or remote MySQL Server instance. Both MS Windows and Linux users should be able to get this to work. ![]() We'll use instead.Īll products described here are available for most popular architectures and operating system. This time, we won't be using MS Office at all. Oh yeah - I once did a write-up on connecting MS Access and MySQL. ![]() So - let's dive in, and see what it takes to use MySQL in the daily office. A lot of the typical problems (resource contention due to locking, file corruption due to crashing application programs, scale limits, and much much more) that you encounter as these applications grow larger, are either not-existent or easily solved using a server solution such as MySQL. In fact, it's probably a good idea to back your Desktop Database applications with MySQL. So, there's not much against using MySQL here. For example, MySQL is not extravagantly resource-hungry, and does not require much maintenance - (not for this purpose anyway). Rather, MySQL is a general-purpose database, so there's no reason at all to dismiss it for typical "Desktop Database" purposes.Įven though MySQL is a server product, MySQL resembles a typical Desktop Database in a number of ways. Of course, I do not want to suggest that MySQL ".is a Desktop Database", because it's not. Yup, you heard me: using MySQL as "Desktop Database", quite like MS Access is being used on many, many windows desktops. I decided it would be fun to write down a few simple tips on how to use MySQL in Office applications. This is true even end-user applications: most MySQL applications I read about, are web applications. A lot of MySQL software development articles focus on the server-side. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |