xBase Scripting
- Thread starter Joe Caverly
- Start date
---- Original Message ----
From: Joe Caverly
| Just a suggestion to enable internal support of xBase Scripting.
|
| xBase Scripting allows using the dBASE/Clipper language as a
| scripting language.
This would also require the user to have installed a program to process the language. Is there any freeware available to do it? BTW, what happened with the FoxPro extensions?
--
Steve
From: Joe Caverly
| Just a suggestion to enable internal support of xBase Scripting.
|
| xBase Scripting allows using the dBASE/Clipper language as a
| scripting language.
This would also require the user to have installed a program to process the language. Is there any freeware available to do it? BTW, what happened with the FoxPro extensions?
--
Steve
Joe Caverly:
Just a suggestion to enable internal support of xBase Scripting.
xBase Scripting allows using the dBASE/Clipper language as a
scripting language.
Steve Fabian:
BTW, what happened with the FoxPro extensions?
Joe Caverly:
Are you referring to the dbf Plugin?
Steve:
No, I am referring to FoxBase and other Fox Software extensions of the
dBase language, e.g. enhanced indexing, database access using SQL.
After MS bought FoxPro, they created Visual FoxPro.
BTW, please do not include the signature when quoting - good email
software won't quote it or anything thereafter. I had to do major
editing to reply properly.
--
Steve
Just a suggestion to enable internal support of xBase Scripting.
xBase Scripting allows using the dBASE/Clipper language as a
scripting language.
Steve Fabian:
BTW, what happened with the FoxPro extensions?
Joe Caverly:
Are you referring to the dbf Plugin?
Steve:
No, I am referring to FoxBase and other Fox Software extensions of the
dBase language, e.g. enhanced indexing, database access using SQL.
After MS bought FoxPro, they created Visual FoxPro.
BTW, please do not include the signature when quoting - good email
software won't quote it or anything thereafter. I had to do major
editing to reply properly.
--
Steve
Hallo Steve Fabian,
It cannot be the task of TCC to create, read and manipulate xbase files of every dialect. There are enough tools around to do that. My original proposal was to include a very simple and basic _indexed_ form of database handling, preferably a dBase dialect, into 4DOS (when I proposed it originally), later TCC. Indexing would have made access to large files like the directory list faster and maybe would have opened new avenues for users of TCC.
By now, I support including access to dirs by the Everything method, which is blindingly fast. I still think database handling would be a worthy addition to TCC, if a suitable DLL could be found.
Best regards,
* Klaus Meinhard *
<www.4dos.info>
It cannot be the task of TCC to create, read and manipulate xbase files of every dialect. There are enough tools around to do that. My original proposal was to include a very simple and basic _indexed_ form of database handling, preferably a dBase dialect, into 4DOS (when I proposed it originally), later TCC. Indexing would have made access to large files like the directory list faster and maybe would have opened new avenues for users of TCC.
By now, I support including access to dirs by the Everything method, which is blindingly fast. I still think database handling would be a worthy addition to TCC, if a suitable DLL could be found.
Best regards,
* Klaus Meinhard *
<www.4dos.info>
Hallo Joe Caverly,
Since the suggestion was originally mine (it dates back to 4DOS days), I felt free to add it to the new feedback forum. Please support it with your vote there.
Best regards,
* Klaus Meinhard *
<www.4dos.info>
Since the suggestion was originally mine (it dates back to 4DOS days), I felt free to add it to the new feedback forum. Please support it with your vote there.
Best regards,
* Klaus Meinhard *
<www.4dos.info>