DBF v3.0, VFP 5, ColdFusion 7.02
FYI I now am able to get a query to run as a free table or as a table in the
database container...as a free table, the result set comes back with
field names as upper case...when attached in the DBC, the result set
comes back with field names in lower case.
However, the table must be in the direct URL path folder. The driver is
not using the DBC file location to find the table. Also, ColdFusion does
not allow the '/' or '\' character in the FROM Clause, so referenced
sub-directories are not possible. (select * from lookupf\lookup)
The stored procedure from the DBC is still not working.
Thanks again for your time.
Paul Hall, Virginia USA
phall@masterymg.com
|
>as a free table, the result set comes back with field names as upper case...
Because all free table is using upper case as column name with a max 10 name length.
>when attached in the DBC, the result set comes back with field names in lower
> case.
Because DBC allows to use lower case or space character as column name with with a max 255 name length.
>However, the table must be in the direct URL path folder. The driver is
>not using the DBC file location to find the table.
Tables should be at the same directory of DBC file.
>select * from lookupf\lookup
You can try: select * from "lookupf\lookup"; or select * from "lookupf/lookup";
>The stored procedure from the DBC is still not working.
It doesn't support stored procedure.
|
Thanks for your answers!
Yes, putting the quotes around the file with path worked!
(select * from "lookupf/lookup")...thanks.
Much of our work involves stored routines...with parameters.
Since DBF v3.0 does not support stored procedures,
is there any other way we can run those routines?
Perhaps a pass-through command...Can we pass
VFP commands through ColdFusion?...for example:
" Do TestMessage.prg ", or
" Do TestMessage.exe ", or
" Run TestMessage.exe "....
is there any other work around you can suggest?
I saw in a note somewhere that your Access driver
supports Stored Procedures...is that correct? If so,
can that driver fire off an EXE that we build with VFP?
|
>I saw in a note somewhere that your Access driver
>supports Stored Procedures...
Yeah. Because MS Access's stored procedures can be translated into SQL. But VFP is a complicate languag at all.
>is there any other work around you can suggest?
Yeah. You can use System.exec function to call some bat files, which will set enviroment and call your VFP program.
|