bb.donnay-software.com

I just saw that Roger is out of the office for a while, so I'll post a question here.

I am an old Clipper programmer that is converting some customers to xBase++ and express++. Roger remoted into my first customer location and demonstrated xDot for DBF manipulation. I have since installed xBase and express at another customer site. The problem is that I can launch xDot at the new site, but cannot do anything from the command prompt without receiving an error about the Include files. I have verified that the DOS path is pointing to the include folder.

Where do I setup the include paths in xDot?

Thanks

tcampbell_nc wrote:I just saw that Roger is out of the office for a while, so I'll post a question here.

I am an old Clipper programmer that is converting some customers to xBase++ and express++. Roger remoted into my first customer location and demonstrated xDot for DBF manipulation. I have since installed xBase and express at another customer site. The problem is that I can launch xDot at the new site, but cannot do anything from the command prompt without receiving an error about the Include files. I have verified that the DOS path is pointing to the include folder.

Where do I setup the include paths in xDot?

Thanks

I found in the readme.txt for XDOT (in the source\xdot fodler) the following:
---------------------
Also, in order to interpret a command, the .CH file for that command must be
loaded by the pre-processor.

XDOT.EXE and DC_Dot() must find STD.CH, DCSTD.CH and DCCUSTOM.CH in the
SET INCLUDE=<include path>. In addition, any .CH referenced in STD.CH,
DCSTD.CH and DCCUSTOM.CH must also be in the INCLUDE path.

Example: SET INCLUDE=C:\alaska\xppw32\include;C:\exp19\include

or

SetEnv("INCLUDE","C:\alaska\xppw32\include;C:\exp19\include")
---------------------

Does that help?