This is an interesting question and I hope you get a lot of responses since I'm sure that I will only cover a small percentage of what you will actually need.
The primary thing to remember is that you are moving from what could be considered a self-contained development environment with a solid GUI, to an enterprise-level database that focuses on performance. So, you will lose some of the convenient features that Access provides while gaining some of the performance that Access certainly can _not_ provide. Let's see if we can hit the main areas you mentioned: A programming environment; I will assume that you are referring to a combination of the forms utility and VBA within Access. You will now have to rely on something like VB to provide all of the GUIs to your DB-based applications, there's simply no way around that. While you may have some advanced users that are comfortable with creating some basic forms and what-not, this will mean almost absolutely nothing in the MySQL environment. A database maintenance utility; A database query tool; The number of products available runs the gamut and I'm sure that furtere research will provide a utility you like. However, DB management in Access and proper DBA management in MySQL are completely different. Access is somewhat "forgiving" on sloppy design, but in order to gain the most from MySQL, it will certainly pay to make sure your DBs are properly normarlized from the very beginning and all of your data types are as they should be. This area should be your largest investment, not only in the time to find a good MySQL management utility, but also in finding and/or training and proper DBA. Personally, I use Mascon for my MySQL DBs, but again, you should research this on your own. As for your advanced Access users, I am afraid that you would have to shut them out of doing most of the functions that they handle now. When dealing with enterprise-wide DBs, it might be best to limit the number of DBAs that have complete premissions to the database. A report builder This will almost certainly depend on how complex your reports are. My experience has been that most intermediate Access users can make the transition to something like Crystal Reports in a fairly quick time-frame. However, a bit more of a learning curve may be required for more complex reports. Also, your queries might need some re-tooling since you would have to run them through the MyODBC driver. Fortunately, VB and Crystal Reports integration is quite easy (I belive the same holds for VB.NET) which would allow you to maintain an "all-in-one" utility for both manipulatiing your data and creating reports. On the other hand, if your reports are not complex at all, then you can simply rely on something like PHP or ASP and have web-based reports. This may not always be the best option for all reports, but if you're only running a few reports and need a cost-effective solution, this may not be so bad. Good Luck! Dennis FILTER: MySQL , SQL , query, etc ----- Original Message ----- From: "Brad" <[EMAIL PROTECTED]> To: "MySQL mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 9:14 PM Subject: Access replacement... I am thinking of a move from a Windows network to Red Hat Linux at my work. I am happy with OpenOffice for spreadsheets, word processing etc but the main problem is replacing MSAccess. MySQL provides a replacement for the database component but that still leaves: A programming environment; A database maintenance utility; A database query tool; A report builder Some of our users have had MSAccess training and are quite proficient in producing simple but usable applications involving: The creation of a database and tables; Forms to populate the database; Queries and reports to display the data. All this in a graphical interface without needing to know SQL or doing any serious programming. They would need to be able to continue doing this in the new Linux environment - is there a suitable "Forms" utility? We also have some "serious" applications written in MSAccess by outside professional programmers. This was partly done to allow the simpler changes (eg reports and screen layouts) to be made by the advanced users in order to reduce costs and delays. I would assume that a "Forms" utility would not provide enough features to be used here. Does this mean that development has to be done in the opensource equivalent of "VB" which may shut out the advanced users from making changes? Regards, Brad --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
