I can extract other data from the table, but the Paradox
datetimes end up as only the date when returned to VFP. I
need to have the complete data for both the start and end
datetimes in order to calculate the duration.
Can anyone provide me with the code snippet to accomplish
this?
Thanks!
Using ...
VFP7
A Paradox 5 table
Microsoft Paradox Driver 4.00.6019.00
... I was able to create a Remote View to the Paradox table
which correctly returned Paradox Timestamp fields as
VFP DateTimes.
Roger
--
Roger Ansell
Adelaide, Australia
My real email address is ransell at senet.dot com dot au
"Bill Whipple" <whi...@ics.uwex.edu> wrote in message
news:0a1001c34afc$d241af80$3501...@phx.gbl...
The only difference would seem to be the Paradox 5.0
driver:
Using Windows 2000 with SP4
VFP7
Paradox 5 table
MS Paradox driver 5.0
ALso, this will be an automated process, so I am not using
a view, but establishing the connection, and then doing a
series of SQLEXECs to get all the tables I need.
The basic code is (Start and End_Time are the TimeStamp
fields):
*** Set up connection to RSBODBC data source
lnHandle = SQLCONNECT("RSBODBC")
? "SQLConnect = " + ALLTRIM(STR(lnHandle))
*** Check for successful ODBC connection
IF lnHandle <= 0
WAIT WINDOW AT 10,5 'Cannot make connection' + CHR(13)
+ 'SQL Connect Error'
CANCEL
ELSE
WAIT WINDOW AT 10,5 'Connection made' + CHR(13) + 'SQL
Connect Message' NOWAIT
tDWarn = SQLSETPROP(lnHandle,"DispWarnings",.T.)
ENDIF
*** Define and execute SQL Query on Paradox SCHED table
SqlQSched = 'SELECT Conf_Ctl_ID, Start, End_Time,
Conf_Name FROM C:\Contex\RSBODBC\sched.db order by
CONF_CTL_ID'
? SqlQSched
WAIT WINDOW AT 5,5 "SQLEXEC... Sched.db" NOWAIT
ExecStatus = SQLEXEC(lnHandle, '&SqlQSched', "Schd")
?"ExecStatus = " + ALLTRIM(STR(ExecStatus))
--- End of Code
I get no warnings, etc. Could this be a problem with the
5.0 version of the Paradox driver? If so, how do you go
back?
>-----Original Message-----
>Hi,
>
>Using ...
> VFP7
> A Paradox 5 table
> Microsoft Paradox Driver 4.00.6019.00
>.... I was able to create a Remote View to the Paradox
>.
>
OK, I did the same thing using SQLExec with the
same result as using a view. So that's not the problem.
Are you sure that the MS Paradox driver is version 5?
Check the Drivers tab in the ODBC Data Source
Administrator.
I'm running on XP SP1 and the version of MDAC
is 2.7 (which AFAIK is the latest version) and the
MS Paradox driver is definitely version 4.00.6019.00.
There's a MDAC 2.7 service pack on MSDN for all
versions of Windows apart from XP which "installs the
same Data Access core components as Microsoft
Windows XP SP1, with the addition of several important
bug fixes."
http://www.microsoft.com/downloads/details.aspx?familyid=9ad000f2-cae7-493d-b0f3-ae36c570ade8&languageid=f49e8428-7071-4979-8a67-3cffcb0c2524&displaylang=en
(Be careful of line-wrap in the above URL)
HTH
Roger
--
Roger Ansell
Adelaide, Australia
My real email address is ransell at senet.dot com dot au
"Bill Whipple" <whi...@ics.uwex.edu> wrote in message
news:083001c34b8e$4d04b820$a601...@phx.gbl...
OK. It looks to be a Windows 2000 ODBC vs Windows XP ODBC
problem.
The app provides me with DateTimes if I use my Win XP
laptop. Windows 2000 is still not working, despite taking
your advice and installing the MDAC 2.7 patch. This
provided a slightly newer driver (v. 4.00.6200.00).
Too bad it needs to run on a Windows 2000 box... :(
>.
>
If not you need to change it to
'SELECT Conf_Ctl_ID, Start, End_Time, ;
Conf_Name FROM C:\Contex\RSBODBC\sched.db order by ;
CONF_CTL_ID'
Is the Paradox drive a single file driver? If it's a database driver there
shouldn't be a path to the table, just the table name.
-Anders
"Bill Whipple" <whi...@ics.uwex.edu> wrote in message
news:083001c34b8e$4d04b820$a601...@phx.gbl...