I am using foxpro in vdos and it works fine. One thing I am trying to do is redirect the directory command to a text file which I then upload to a database file. If there is a file which breaks dos 8.3 naming commands by being too long it does not appear when I do the run dir command in foxpro. Vdos will not accept dir /x or dir /d nor will it allow me to use wild cards in the rename command when I try to truncate the offending portion of the file name. It say NO WILDCARDS! so I gather this is a known issue. Is there a way in vdos to do this or should I find out how to run a pre processor dos batch file that will truncate them before opening them in vdos
The command line processor in vDos is limited at supporting commands and options. Though not considered an issue, vDos is primary meant to run DOS programs. Certainly it won’t allow you to use a LFN. You could use CMD to redirect to a LFN (mind to enclose the whole command line, including the redirection, in quotes). But why not stick to SFN in the FoxPro program itself?
Thanks for your help I was trying to use the run command in foxprox to directly run the dir command you are using the cmd command (run cmd) to activate the command from foxprox and from there the dir command works fine
BTW I have also seen the page fault issue - when using foxprox - I am unclear if the release that helps this issue is active or still beta hard to pinpoint when it will occur
I have the example only in a multitask environment (in a DO WHIL) and immediately taken from my program without further analysis for now. The options all have a function within them (once figured out), but I would not know that anymore exactly about what and how on this moment.
Everything has a reason to do so in my case.
For me it is about allowing dBase to be disconnected from the external assignment.
Doing the assignment immediately would mean that you had to wait with the program to be able to do anything else. From there start the START.BAT from RUN ().