🚀 go-pugleaf

Marco

tanti grazi encore - I think :)

Your input has been very helpful and I think we have a better idea now
of which way to go.


mrocciNOSPAM@tin.it (Marco Rocci) wrote:

<snipped>
>>
>>Do you have any feel for how comprehensive LOCALSQL is?  For instance,
>>if Paradox was used, will LOCALSQL place limitations on what can be
>>done - or are all the "normal" database functions catered for?
>
>LocalSQL covers most of the "normal" database functions.  A complete
>list of unsupported SQL language elements can be found in LocalSQL.hlp
>(if you have the updated help file).
>
>I'd say that the most useful thing missing is the ability to create
>and mantain constraint via SQL.  Be aware that you *can* have
>constraints on the Paradox table (appropriate level)... you just can't
>create tables with CHECKs and FOREIGN KEYs by using a TQuery.
>
>I have to say that I don't create or restructure dbs by using Delphi
>apps anyway... so I can live without it.
>
>Your real issue is speed.  To have Paradox scream on a LAN you might
>have to use TTables and indices instead of TQueries.
>
>If you go the InterBase way... you can easily scale down to Local
>InterBase Server.  You can deploy that for 20$-60$ per seat (depending
>on how many you intend to deploy).  It's fully compatible with the
>InterBase Server (the gdb files can be copied and opened by both).
>Administration is easy.  It might be a bit slower than Paradox on a
>single user PC, but it really means you have to add
>*not*a*single*line*of*code* to make it work on both.
>
>Regards,
>
>--
>Marco Rocci
>MicroEra srl
>Turin, Italy
>-----------------
>vota contro lo SPAM su: http://www.politik-digital.de/spam/


Tony Lees

Put a dash instead of dash if emailing me