Problems with version 2019.05.01 (dbase-program)

[drschnagels]

Hi !

I'd like to help resolving problems I found so far with the new version.

1) Does not run faster in this case:
An old dbase order and hour collecting for craftsmen program sums up lots of hours between 2011 and 2019. Old version needs 36 seconds. New version 50 seconds.

It's simply summing up every work day (01.01.2011 up to today), to each "order ID number" and all the craftsmen hours.

Why is summing up now slower?

How can i provide additional info about this?

2) Please see attachment

New version seems to have replaced ASCII characters???

Left side: New version, strangely the red characters change when summing up again and again!!

Right side: old version. The correct character which does not change, after running the same method in the program again and again.

Why does the new version randomly change characters?

3) New version: now needs FRAME = on to display a frame. Old version displays an error.

4) New version: does not print at all. (our config: LPT1 = SEL: "" RAW)

Old version works flawlessly even with printing to a PDF printer.

On screen view still works in the new versions and shows the same results (see 1) above).

Maybe printing suddenly does not work because characters are switched? See 2).

I used a backuped new directory in which i simply exchanged the .exe files between both versions (always re-copied changed files).

And compared the files between both versions with Total Commander, content compare (see screenshot).

Obviously printing is super important and I don't understand why it does not work anymore.

Thanks for the great program!

Michael

Attachments:

[emendelson]

You may have the versions backwards. The new version does NOT use the frame= option at all. It was only used by an older version (2017, I think). The new version always displays a frame (except, of course, in full-screen mode) and gives an error message if you have frame=(anything) in config.txt.

Please make sure you are using the new 01.05.2019 version and try these tests again. Use the VER command at the vDos prompt to make certain which version you are running.

[Jos]

My guess: At installation you chose NOT to update to version 2019.05.01.
So you got the Base version, what is essentially 2017.08.01. Plus some last corrections, minus printing and executing Windows programs.

Jos

[drschnagels]

If this is true, it is really unfortunate.
Ill check that later.

I downloaded the new version, installed without "updating".
Reason: I of course dont want to change our working production installation. So i choose a new path.
I copied there our program, database and license. Why does the download of 2019 not give me the 2019 version?
I'd never change our working installation without testing before. A bug or any kind of calculation errors which we don't find would be very bad .

It should be made very clear while installing that Im not getting the 2019 version. Or split the setups into two.

[drschnagels]

Im super confused now.

Both are 2018.5.1.

But they dont have the same icon!

Our current production version is the one with the blue icon.

Attachments:

[Jos]

I changed the update option a little in the installation program. Though the download page already states:

“The downloaded installation program vDosSetup will install the Base edition of vDos and default to update that to the 2019.05.01 version. The Base edition is 100% opensource, basically vDos 2017.08.01. However w/o internal printing and executing Windows programs, no later improvements and unsupported like other older vDos versions.”

Both version 2018.05.01 and Base were initially created/released that date, Base has the icon of 2017.08.01.

Jos

[drschnagels]

I do understand now of course.
It's still confusing and I have to deal with being super super careful not to overwrite our current working configuration.
Ill double backup everything and try again.

[Jos]

Certainly vDos users with a network configuration will have copied essential vDos stuff (one vDos.exe, eventually more config.txt and autoexec.txt files) to the central fileserver.
Little sense to go beyond a warning overwriting the default local C:\vDos directory. More extensive precautions, more confusion?

Jos