Article View: borland.public.vdbase.data.sql
Article #160Re: Date field in sql builder
From: Steve Koterski
Date: Fri, 05 Mar 1999 00:00
Date: Fri, 05 Mar 1999 00:00
47 lines
3098 bytes
3098 bytes
On Fri, 05 Mar 1999 14:01:07 GMT, bergishagen@vip.cybercity.dk (Ivar B. Jessen) wrote: [...] >Please also see my comments in borland.public.vdbase.forms, subject >SQL selecting on date, Fri, 19 Feb 1999. I'll try to find the cited information. >>I do not have access to a non-US BDE/Delphi/computer. > >Your US computer will probably be ok, but you should use Visual dBase >7.01 rather than Delphi to make any test.<G> No. Local SQL is a facility of the BDE, not of any one front-end application: Visual dBASE, Delphi, C++Builder, or what-have-you. The behavior of local SQL should be consistent under *all* using application front-ends. A BDE-using application passes an SQL statement to the BDE in the form of a string, as a parametere to one of the BDE API functions for executing queries. These API functions include DbiQExec and DbiQExecDirect. So it is not Visual dBASE that is executing the SQL query, but the BDE. A date literal of "03.05.1999" should be the same whether passed to the executing API function by Visual dBASE or by Delphi. A difference like the one behind this thread could happen, though, if the application front-end was doing some hanky-panky with data values between the user interface and the BDE. That is, it is conceivable (to me, anyways) that Visual dBASE is doing something function with these date literals like reformatting them using Windows configuration settings before passing the SQL string to the API function. If such a thing were occurring, the behavior would not be part of local SQL. It would be peculiar to Visual dBASE. As such, it would need to be covered in the Visual dBASE documentation and not in that for local SQL. This is because the behavior would only manifest itself when SQL is used from Visual dBASE and not from other BDE-using programs like Delphi and C++Builder. To document it where non-dBASE users are going to see it and not see the behavior would just sow confusion. ////////////////////////////////////////////////////////////////////////// Steve Koterski "My problem lies in reconciling my gross Technical Publications habits with my net income." INPRISE Corporation -- Errol Flynn (1909-1959) http://www.borland.com/delphi
Technical Details
Message-ID:
<36e6446e.15983711@forums.inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<7bk1bs$2i77@forums.borland.com> <36ddce30.1329713@forums.borland.com> <36e4e115.7047839@forums.inprise.com> <MPG.114868a19e128ae3989fa1@forums.inprise.com> <36e2ca7c.5461887@forums.inprise.com> <36dfd632.210165@forums.inprise.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5a1,9c0ce2ccf9b5c6e5 X-Google-Attributes: gidff5a1,public From: skoterski@NOSPAMinprise.com (Steve Koterski) Subject: Re: Date field in sql builder Date: 1999/03/05 Message-ID: <36e6446e.15983711@forums.inprise.com> X-Deja-AN: 451694453 Content-Transfer-Encoding: 7bit References: <7bk1bs$2i77@forums.borland.com> <36ddce30.1329713@forums.borland.com> <36e4e115.7047839@forums.inprise.com> <MPG.114868a19e128ae3989fa1@forums.inprise.com> <36e2ca7c.5461887@forums.inprise.com> <36dfd632.210165@forums.inprise.com> Content-Type: text/plain; charset=us-ascii Organization: INPRISE Corporation, Technical Publications Mime-Version: 1.0 Reply-To: skoterski@NOSPAMinprise.com Newsgroups: borland.public.vdbase.data.sql