PDA

Click to See Complete Forum and Search --> : Strange problems and eSellerate

longwolf
Nov 14th, 2006, 10:19 PM
I have a client wanting me to make alterations to his app.

When I tried to run his source code I got strange errors.
For instance, VB isn't recognizing commands like Ucase and Format.

He gave me a link to his installer package and it worries me even more.
It asks if you want to install some files that are older than the ones on my system then asks if you want to install some "other files" without telling what they are or what they're for.
I canceled the installation.

Now I find out that the programs missing references are for something called eSellerate.
Apparently it's their installer that I tried to run.

I'm on the road and without my re-installation disks, so I'm a bit afraid of installing their stuff just do this guys job.

What do y'all think?
randem
Nov 14th, 2006, 11:52 PM
His installer package is not packaged properly. He has no idea of what he is doing with regards to installations.
longwolf
Nov 15th, 2006, 12:02 AM
I just hear back from the client, the installer was made with NSIS, Null Soft Installer Script and with the UPX ultimate packer.

I still can't figure out why Ucase and Format aren't working.
All of the VB dependencies are in place.
randem
Nov 15th, 2006, 12:08 AM
The VB runtime files are not up to date in the installation package or you would not be getting that message. The dependencies may be even from the wrong OS. I would not trust that installation at all.
longwolf
Nov 15th, 2006, 01:19 AM
I canceled the installation before it did anything and am only trying to run his source code now while bypassing the calls for the eSellerate dll's.

I'm not having the Ucase and Format problems with another instance of VB6 that's running.
si_the_geek
Nov 15th, 2006, 10:19 AM
The issue is that the project has missing references (the DLL's). This causes seemingly random errors with other functions (like Ucase/Format/Left), as VB is not sure which library to get them from (even tho it should know).

To fix the errors, you need to fix (or remove) that reference. In order to fix the reference, you need to install the DLL's.. it sounds like the installation package isn't very good tho. :(