Article View: borland.public.vdbase.data.sql
Article #318Re: SQL Question
From: Craig Veal
Date: Fri, 01 Jan 1999 00:00
Date: Fri, 01 Jan 1999 00:00
27 lines
1647 bytes
1647 bytes
Geoff, I finally beat the beast, getting help from Alan's OODML.HOW (the params property did it). Anyway, the end results are essentially th same as a DMD would have been (all created via drag-n-drop). Each rowset (except the first) has a master-detail link with the rowset above it. The question I now have is why do you say SQL with .DBF is not recommended when the SQL designer is the same one that would be used to create the DMD? Am I not seeing the forest because of all the trees? Thanks. Geoff S. Wass wrote: > The use of SQL with .DBF tables is not normally recommended. The > recommended method for .DBF tables it to use a dataModule with the > master-detail type of linking. There are two advantages: (1) is runs > at least as fasts as SQL if not faster; (2) the result is always > updateable while SQL generally results in read-only views. > > Re-do this using a dataModule and master-detail linking. It is easy > and worth the effort. Craig Gator Custom Software ------------------------------------------------------------ "If A Computer Crashes In Cyberspace, Does It Make A Sound?"
Technical Details
Message-ID:
<368DB324.ABB94B24@cfi.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<368D3114.82F8A14A@cfi.net> <368D954E.28E39F7B@ibm.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5a1,2e1c13aae25a9cd4 X-Google-Attributes: gidff5a1,public From: Craig Veal <cdveal@cfi.net> Subject: Re: SQL Question Date: 1999/01/01 Message-ID: <368DB324.ABB94B24@cfi.net> X-Deja-AN: 427921354 Content-Transfer-Encoding: 7bit References: <368D3114.82F8A14A@cfi.net> <368D954E.28E39F7B@ibm.net> Content-Type: text/plain; charset=us-ascii Organization: Gator Custom Software Mime-Version: 1.0 Newsgroups: borland.public.vdbase.data.sql