Re: Drowning in Modules - Suggest those for DB App

While I agree with you on replacing the jet DB engine with the more robust/Featured MySQL, I'd like to suggest that the "bathwater" - i.e. ACCESS be retained as a reporting and end-user GUI tool, although the "baby" is being replaced/upgraded.

Access should still be able to link via ODBC, to the MySQL db, so there is probably no need to re-invent the forms and reports, if they already exist.

P.S. Hmmm..Interesting .. I just realized how well the "bathwater" analogy fits into your "drowning" scenerio.

Earth first! (We'll rob the other planets later)

Comment on Re: Drowning in Modules - Suggest those for DB App

Replies are listed 'Best First'.
Re^2: Drowning in Modules - Suggest those for DB App by castaway (Parson) on Oct 12, 2004 at 06:53 UTC
I can't help but ask why you say that MySQL is more robust/featured than MS Access. Do you have evidence for this? C.	[reply]
Re^3: Drowning in Modules - Suggest those for DB App by tilly (Archbishop) on Oct 12, 2004 at 07:18 UTC
Here is a random opinion. In my experience Microsoft Access in multi-user mode has some nasty race conditions. Put it under load and it will randomly lock up and fall over. That would make it significantly less robust than MySQL. If you value standards compliance, MySQL wins over Access. (eg Should like use a * or % as the wildcard?) Likewise MySQL does not tie you to a specific OS platform. I have no idea which has a better optimizer. I am certainly unimpressed with the Jet engine. But I've never thrown complex queries at MySQL, so I can't say how it compares. But on features, I'd suspect that Access wins. If not in features that I care about...	[reply]
Re^4: Drowning in Modules - Suggest those for DB App by Yendor (Pilgrim) on Oct 12, 2004 at 12:47 UTC
I am certainly unimpressed with the Jet engine. I've heard the following said about the MS Jet database engine, and my experience shows that it's reasonably true: The Jet database engine, like its namesake, both sucks AND blows. ;-) -Yendor IWeThey HOPE Ride	[reply]
Re^4: Drowning in Modules - Suggest those for DB App by dragonchild (Archbishop) on Oct 12, 2004 at 14:33 UTC
I have thrown complex queries at both Access and MySQL and MySQL wins hands down. It's not even a contest. Heck, MySQL out-performs a comparable Oracle 9i system in certain situations, which impressed me more. This is why our datawarehouse is on MySQL 4.1.4 and not Oracle 9.2.0.5. shrugs Being right, does not endow the right to be rude; politeness costs nothing. Being unknowing, is not the same as being stupid. Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence. Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.	[reply]
Re^3: Drowning in Modules - Suggest those for DB App by dga (Hermit) on Oct 12, 2004 at 22:18 UTC
If 'multi-user' is a 'feature' then I think we have a clear winner. There are packages to patch on to Access which allow 'multi-user' though I don't know if/how well they scale. Also direct network access might be construed as a feature if ODBC isn't desired as the interface. Also, some may consider portability a feature. Authentication and access control are also widely considered to exist in the 'feature' space. I am sure there are others in addition to this very brief list.	[reply]