Discussion:
File with a "." in it
(too old to reply)
Jerome Dufour
2018-06-26 20:08:21 UTC
Permalink
Hi everybody,

I'm in a transition from windows DOS to dbDOSPRO from dBase to continue working with dbase/clipper on windows 10 64 bits. Here my problem:

I have to use a file generated by another program and this file has 2 extensions (Ex.: usa.fil.dbf). I worked around this with Xcopy from DOS (on XP OS) but now, xcopy doesn't work with dbDOSPRO. Neither this DOS or dBase "see" the file. I have tryed things like "copy file" or "rename" from clipper but it's always return an illegal path error. Does anyone have ideas?
lohen
2018-06-26 20:28:13 UTC
Permalink
Hi Jerome,
Post by Jerome Dufour
Hi everybody,
I'm in a transition from windows DOS to dbDOSPRO from dBase to continue
I have to use a file generated by another program and this file has 2
extensions (Ex.: usa.fil.dbf). I worked around this with Xcopy from DOS (on
XP OS) but now, xcopy doesn't work with >dbDOSPRO. Neither this DOS or
dBase "see" the file. I have tryed things like "copy file" or "rename" from
clipper but it's always return an illegal path error. Does anyone have
ideas?
In the same corner there are vDos and vDosPlus (both free) which do what
dbDOS does, but for text mode only (also for 32/64bit Windows, including 10)

vDosPlus (http://www.columbia.edu/~em36/wpdos/vDosPlus.zip) supports Long
File Names; combined with the LFN library (for CA-Clipper;
http://www.engwall.com/clipper/lfnlib.htm) your 16bit DOS application can
access LFN's (like usa.fil.dbf actually is)

However, as mentioned in the LFN.LIB documentation, opening a .dbf with a
LFN (USE ...) is not completely supported, but I understand that is not what
you want; just copy the LFN into a SFN and USE ... (of course) can deal with
it

Here are the pointers:

vDos http://www.vdos.info/index.html and on sourceforge
http://sourceforge.net/projects/vdos/
vDosPlus http://vdosplus.org/ and on sourceforge
https://sourceforge.net/projects/vdosplus/

dbDOS (and *PRO) is derived from DOSBox, just as vDos (and vDosPlus which is
derived from vDos)

Else! If your app needs to do graphics, use DOSBox SVN-lfn
https://sourceforge.net/projects/dosbox-svn-lfn/?source=directory (instead
of plain DOSBox)

In either case, your CA-Clipper program needs above mentioned LFN.LIB by
Klas Engwall

The three virtual machines above all support CA-Clipper protected mode apps

HTH

best regards,

lohen
Johan Nel
2018-06-26 20:30:47 UTC
Permalink
I would really suggest you consider moving to [x]Harbour, rather than
trying to "fudge" using Clipper for the immediate future.  In the long
run start looking at XSharp.  They busy developing a Harbour interface
in XSharp.  https://www.xsharp.info/ which will make your applications
100% .NET
Post by Jerome Dufour
Hi everybody,
I have to use a file generated by another program and this file has 2 extensions (Ex.: usa.fil.dbf). I worked around this with Xcopy from DOS (on XP OS) but now, xcopy doesn't work with dbDOSPRO. Neither this DOS or dBase "see" the file. I have tryed things like "copy file" or "rename" from clipper but it's always return an illegal path error. Does anyone have ideas?
--
*Johan Nel*
George, South Africa
j***@gmail.com
2018-06-27 10:37:01 UTC
Permalink
Post by Jerome Dufour
Hi everybody,
I'm in a transition from windows DOS to dbDOSPRO from dBase to continue working with dbase/clipper on windows 10 64 bits.
I use vDosPlus for running Clipper 5.3 and dBase IV 2.0 apps on my Windows 7 system, and have not had any problems.

While I have used dbDosPro 5, I find that vDosPlus is much better for my Clipper and dBase IV 2.0 apps.

I find it easier, though, to re-compile my Clipper code using Harbour. It supports LFNs, and other OS APIs. That way, I can run the compiled apps on a Microsoft Windows system without using dbDosPro or vDosPlus.

Another bonus for Harbour is that the same Clipper code can be compiled and executed on a Linux system, using Harbour for Linux.

Harbour Wikipedia Page: https://en.wikipedia.org/wiki/Harbour_(software)

Harbour Download Page: https://harbour.github.io/

Most 3rd party Clipper libraries have been converted to, and are included with, Harbour.

Joe

Continue reading on narkive:
Loading...