Dbase III Plus

[chris]

Hello,

This is my first post here.  Thank you in advance for any help!

I have been nursing a Dbase III Plus multi-user program through the the generations of 32bit.  I'm am now testing with vDos on 64bit OS and most everything is working with a few fixes here and there.  The main issue I am have is with the following error message:

*** Execution error on STR() : Out of range

The command that invokes this message is:

ltrim(str(variable))


When I invoke the same command using a NTVDM window the command performs as it should.

I'm am using the latest vDos version.  Would an older version be better to try?  Thoughts?

Sincerely,
Chris

[Jos]

You didn’t mention this happens always or with specific values of variable.

Add FPUAWARE = 2 to config.txt and see if that fixes the problem.

Jos

[chris]

Hi Joe,

The execution error occurs with both a numeric and date variable.  I've tried various values of variable and all report the STR() execution error.

I added the line FPUAWARE = 2 and upon launching vDos a message box popped up and said "No valid option FRUAWARE" after which I must "Endtask" to close the attempting vDos window.

Thank you,
Chris

[Jos]

I also tried several values with STR(), though no error. So I thought it would be with some specific calculated values.

FPUAWARE is a valid config.txt option of vDos. Even if it wasn’t, you would get a message box with an OK button and close cross.

Download and install vDos 2022.05.01 again, vDos.exe would be corrupted?

Jos

[chris]

Hi Jos,

Thank You!  You are correct!  I may not have been using the latest version.  I started from scratch with a fresh download and was able to add the "FPUAWARE=2" clause.  I had trouble at first launching vDos but then I added "ADMIN=ON" to the config.txt and every is working fine.  I now longer receiving the "Execution error on STR() : Out of range" and the program is working as it should.

I will be moving this test to a secondary server at the work location to test printing tasks within the program to specific printers on the network.  I will then move to primary file server for actual use.  I will license a network version as soon as I can get all this done.

Thank you for your help, much appreciated!

Sincerely,
Chris

[Jos]

Before (instead of) installing vDos at workstations, have a look at: vdos.proboards.com/thread/656/accessing-data-network-drive-using (Comp1 being your server).

More general: www.vdos.info/faqs.html - Advanced - A portable DOS application.

Only a shortcut to vDos.exe at the server would essentially be required at the workstations.

Jos

[chris]

Hi Jos,

In my home test environment I an using a NAS unit as my server.  I have moved the vDos folder from the local C: drive over to the NAS and was able to successfully launch the program.  I am unable to launch the program from another pc simultaneously pointing to the same vDos folder.  Either one or the other pc works just one at a time.


Chris 

[chris]

Hi Jos,

I am using win 11 pro and a win 7 pro laptop to test simultaneous use of the program from the NAS and both are launching the same Desktop shortcut.  The win 7 laptop requires the "ADMIN=ON" but the win 11 laptop is indifferent to that command.

Chris

[Jos]

The "ADMIN=ON" requirement at your laptop merely indicates a security problem: ALL programs are executed with elevated rights, WITHOUT notifying you.

Don’t know whether you have to login to the program. It would have to be given an user (or PC) name to run multi-user?
If no login, an environment variable is set beforehand (like SET USER=ABC, XYZ, …). Or a command line parameter starting the program (like u=ABC, XYZ, …).
If so, add that to the Target property of the shortcuts (\\server\share\vDos\vDos.exe ABC). Then use %WIN_VDOS% in autoexec.txt to set the environment variable or command line parameter.

Jos

[chris]

Hi Jos,

The program I'm launching with vDos is Dbase II Plus. One at the Dbase (dot) prompt I execute a PRG program via a "Do f:\folder\program.prg". No user name is required to launch. Also, might you have an example of the using the %WIN_VDOS% in the autoexec.txt? I just need both laptops to start an instance on Dbase. The Dbase I am running is DBA Administrator network version of Dbase III Plus.

Thank you,
Chris

[Jos]

So you start dBase by "dba #df=x:", where x: is the shared drive letter set in DBA Administrator?

Ensure you first CD to the DBA directory and x: is a valid drive letter in vDos.

If you start vDos by for instance "….vDos.exe ABC", ABC will be assigned to the WIN_VDOS environment variable. So you can do "ECHO vDos parameter was %WIN_VDOS%", or "dba #df=f: %WIN_VDOS%"”.

Jos

[chris]

Yes, DBA is the command. I have tried both with and without adding "#df=x:" without success. I do believe that it has to do with the DBA version checking for the number of valid instances of the dbase lan pack. In our NTVDM world we are able to launch 6 instances of dBASE but with vDos only one instance at a time.

To test this theory further I attempted the same exercise with dBASE V 5 and it works just fine with vDos and able to launch multiple instances. We prefer the dBASE III + (dot) prompt interface better.

I will try further with %WIN_VDOS%. I will start testing printing tomorrow.

Chris

[chris]

Also, this version of dBASE "DBA" also installed a check folder called "DBNETCTL.300". I'm sure this is the folder that contains the instance check for dBASE. Not sure if vDos has the same access to this as NTVDM does.

Chris

[Jos]

You would have to start "DBA #df=vDos_drive_letter_of_the_DBNETCTL.300_folder:". So DBA can locate that folder.

Seems to me the Command Window of dBaseV is a flexible successor of the static dot prompt interface.

Jos

[jamesb52]

I never hesitate to suggest that dBase IV users keep a copy of SharkBase on hand in case they encounter the limits of dBase.  SharkBase (network version of VP-Info) can handle unlimited dBase/Clipper files and fields and can take over if one runs into any dBase functions that are annoying. Cheap insurance!