A Windows 2003 Sever Work Around Needed if possible

Robert Haussmann haussma at nextdimension.net
Fri Aug 17 16:31:39 PDT 2007


If you are on 5.0.14 or later, you could try:

SET PFLONGVARDOT=OLD

>From the help file:

filePro used to accept a period in variable names.  
This is now not allowed (it never should have been 
allowed in the first place), in order to permit enhanced 
functionalities.  To revert to the old behavior and 
allow periods in variable names, you can set 
PFLONGVARDOT=OLD.  Note, however, that this will 
disable certain features, such as access to ODBC 
and biometrics, which require that periods not be allowed here.
Version Ref:	5.0.14

Bob Haussmann
Tabor Children's Services, Inc.

-----Original Message-----
From: filepro-list-bounces+haussma=nextdimension.net at lists.celestial.com
[mailto:filepro-list-bounces+haussma=nextdimension.net at lists.celestial.com]
On Behalf Of Sharon Miller
Sent: Friday, August 17, 2007 6:46 PM
To: filepro-list at lists.celestial.com
Subject: A Windows 2003 Sever Work Around Needed if possible

A while back one of my  customers migrated from SCO Unix Filepro to
Windows 2003 server with the  Network version ofFilepro. After some
minor issues and setup  everything has been running pretty smoothe with
the exception of @CB which he had to give up... ( a sad thing to loose)
. He has come up with another more drastic  problem.....

Most of his files are longer than 8.3 characters.... This has not caused
a
problem, until now. Everything in the runtime side has worked fine. It
can still pull up the files even though thet do not follow the dos
convention...
But now he needs to change a field length in the define mode.... Since
the define mode does not see any file that has a period in it, it can
not pull ut file in  the define mode to increase length or add screens
etc.... is
there away around this. I don't see why the runtime (dclerk, dxmaint,
and dreport) see the files correctly but not the dcabe and define.... I
understand the old dos limitations of not being able to create a file...

but if the file is already there, can't filepro update it..... IE the
need
to add fields, change field lengths, add new screens etc.

If you could give me a work around without renaming the files, this
would be appreciated. The remaning of the files would cause a great
inconvience due to the fact in the processing there are many lookups and

all would have to be changed manually. If it were only one file, it
might not be too bad but there are close to a hundred files with lookups

in all.

I do not need to create new files with names longer than 8.3 charcater
limitation just be able to modify the ones that migrated over from unix.
If filepro can not open the file with the define mode is there a dos or
windows command that you could alias the file so filepro could see
it.... I link under unix you can ln (link files to have more than one
name... is there something like this under the windows environement) to
make some changes to these files.

Sincerely yours

Sharon Miller
Florida Software & Data Systems Inc



_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list