[AccessD] .NET

To add to that, OpenOffice has a tool similar to Access (uh yeah, whatever),
that gives a GUI to MySQL.  I read a lengthy article about the extremely
complicated setup involved, but give it a few versions, and who knows...


>  -----Original Message-----
> From: 	Arthur Fuller [mailto:artful at rogers.com] 
> Sent:	Monday, February 24, 2003 10:18 AM
> To:	accessd at databaseadvisors.com
> Subject:	RE: [AccessD] .NET
> 
> >>ALL of that stuff is the difference between just using java and writing
> to the .net environment.  Development is ALWAYS about cost.  In the end,
> managers don't care if they have to pay $50k for MS licenses if the app
> they need developed costs $50k, when the alternative is to not pay the
> $50K to MS but pay $500K to develop their app.  And that is the Achilles
> heel of the "opensource software" (free software to the unknowing).  The
> stronger the foundation you build your app from, the less you have to do.
> Write Access, or buy it?  Write SQL Server or buy it?  Write the .net
> foundation or buy it?  Try doing any of this in Java and come back next
> century when you are ready to start building your actual app.
> 
> Argument by straw man, JC, reflecting your unacquaintance with the the
> Linux world more than the actual situation. 
> 	1.	Why write Access when there are several IDEs that are
> approximately equivalent. Borland's JBuilder and Kylix come to mind, the
> former an IDE for Java and the latter an IDE for Delphi (sort of). Both
> products are extremely high quality. There are similar offerings from IBM
> as well.
> 	2.	Should you go the Java route, you don't have to write the
> .net foundation. Sun did it for you.
> 	3.	You don't have to write SQL Server. If you want speed use
> MySQL. If you want transactions, triggers &c use PostgresSQL.
> 
> Arthur
>