Database has wrong version # (db4187 pro 4189) (44)

T

Thyezer

New Member
Database has wrong version # (db4187 pro 4189) (44) SOLUTION PROVIDED 2-19-10

Trying to create a shortcut to a .w but am receiving that error? How can my db version be incorrect all of a sudden? Any ideas as to what creates this? Any way to resolve? Your help is greatly appreciated!

Structure is as follows:
Progress 9.1D installed on Vista machine.
DLC folder is on C:
.db is located in DLC/hardy folder.
.w is located in same DLC/hardy folder.
Prowin32 is located in DLC/bin folder.

SHortcut:
C:\DLC\bin\prowin32.exe -p C:\DLC\hardy\hardymain.w -db C:\dlc\hardy\hardy.db -1

Start up in:
C:\dlc\bin

Thanks for your help!
 
Not sure what you mean by 'shortcut' or what OS is involved, but I am guessing that its Windows, you have multiple Progress versions on your PC, and you are running a different version (Progress client) than you think you are running. So, try to track that down.
 
By shortcut, I am referring to selecting an icon (shortcut) that will run an application without having to open up appbuilder first. The machine is Vista as shown above, and there is no way that a second version of progress is running on this machine...just formatted and installed 9.1D myself. Could it be in the path of my shirtcut link? I can't seem to find the proper information to direct me if that is indeed correct?
 
Running version 9 of Progress on Vista may work but it does boggle the mind.

Where did the db come from?

Was it originally a 9.1D database?

Or was it, perhaps, a 9.1C database?
 
Hmmm. The information you pasted above looks reasonable to me. A couple of more thoughts:

1. Are you sure hardy.db got created from the same Progress install?
2. Try running prowin32.exe directly and issuing a CONNECT against hardy.db.
3. Try running a .W that does a CONNECT, rather than using the -db parameter. Both should work, though.

FYI, here are the shortcut setups that I use.

#1: I always CONNECT once I'm inside here. I don't think the extra things I have that you don't would have any bearing on your issue:

C:\dlc91d09\bin\prowin32.exe -inp 8192 -tok 8192 -basekey "INI" -ininame "c:\progressini\gt.ini"

#2: This one runs a .W directly. The .W issues a CONNECT.

C:\dlc91d\bin\prowin32.exe -p s:\src\ini\dev\V91dpad.w

Oh and one last thing, you're likely to get flamed on here for using a Progress version from decades ago. Not by me though - as you can see, I'm a 9.1D man myself. Or more correctly, my employer is :)
 
Within App builder I can connect to hardy.db and all works just fine. The only installation I have available was/is 9.1D and I even verified through Appbuilder/help.about appbuilder that the version is still 9.1D.
Just walking through the steps again to show what I did:
1. Developed application in 9.1D using AppBuilder.
2. Saved file as .w
3. Tested file by connecting to .db (hardy) on local machine. (tested fine)
4. Created shortcut from .w file to be used to connect to .db and run application without opening AppBuilder first.... (I think this is somehow the culprit)
5. Used previous information to link to .db and run app (C:\DLC\bin\prowin32.exe -p C:\DLC\hardy\hardymain.w -db C:\dlc\hardy\hardy.db -1)
6. Database was created from this version(9.1D) and is in working order when used from an OPEN appbuilder.

And I hear ya Greg... normally 9.1D does everything we need. It may be old...but you should see our hardware :)

Thanks for any suggestions.
 
Try to create a shortcut just to connect to the database, see if that gives you any errors.
c:\dlc\bin\prowin32.exe -db c:\dlc\hardy\hardy.db -1

If that works fine, just search for hardymain.r file (could be an old one or a corrupt file). Either way, rename the file or move it, so it runs the source and not the compiled program. See if you get the same error.

HTH
 
I have run several searches and there seems to be NO hardymain.r (there is a .w of course...but no .r file). Is there a way to verify what version the .w is created in? I cannot believe that it shouldn't be 9.1D, but just curious?
 
My embarrassment!

Here is the solution... a few "" will do the trick!
I uninstalled progress....reinstalled.... same problem.....
Finally, I looked at the Prowin32.exe shortcut and realized that the path was surrounded in quotes (""). So I made a shortcut from the prowin32 file and retyped the other locations to where I had moved them (probably not needed but I was trying everything)....
and it worked....
Here is the shortcut solution:
"C:\Program Files\PROGRESS\bin\prowin32.exe" -p "c:\progress\wrk\hardy\hardymain.w" -db "c:\progress\wrk\hardy\hardy.db" -1

Now... only problem is that when i run the app and select "Exit" from the app to quit (Quit function when selected), it gives me an error and opens up the procedure editor window...

INVALID character unit value 336, Changed to 320. (4132)

Much better than before, but still a problem that should be easy to fix....right guys????

Thanks for all the input and help....any suggestions on this problem?

SOLVED.... after my "apply "close" to function", I just added the command Quit. I Just love simple fixes...and it only took 10 hours to resolve ;)

Thanks again! Hopefully my mistake can help another one day!
 
You must log in or register to reply here.
Back
Top