Testing my application

Hi people. I have made a vb application that I will soon distribute. I havn't got the chance to test it on many computers yet.

What i'm looking for is not beta testers, I only need someone to download my .exe and run it to see if I have missing .ocx or stuff like that.

If you're insterested in this short duty that would really help me out, contact me at:

[email protected]
ICQ: 5143968 (Krass)

(So far I saw my application working on 98 only. I tried it on 95 and I still have problems with MDAC. Win95 users could be very useful to me)

Thanks again!

If its a problem with MDAC, make sure the Win95 users have installed and updated their windows, or just chose it as part of your distribution packaging. but how big is the EXE anyways, and what kind of application is it?

Quote:

---

Originally posted by kb244
If its a problem with MDAC, make sure the Win95 users have installed and updated their windows, or just chose it as part of your distribution packaging

---

The application is now 21megs. Using many .ocx and it has a couple of .mdb files. It's an application dealing with life insurance products, for a company I worked for earlier this year.

You see, on Windows 95, my install starts by telling the user that MDAC must be installed before proceeding to the installation of the program. The user clicks OK and the MDAC installation starts. Everything seems to work but if I try re-installing it, it will say AGAIN that mdac must be installed or repaired... and it'll say this everytime. (unlike Windows 98, which installed it the first time and never bothered me again). This is driving me mad because most of the users will be running it on older laptop, on windows 95.

Any further suggestions on this?

(what did you meant by updated their windows?)

that I am unsure about, but updating windows like installing updates, and patches, if you download at least IE 4.0, then goto windowsupdate.microsoft.com, you can download all the updates for your version of IE and windows, also on your product, have you considered cleaning out some of the code so that it wont use so many activeX, I may recomend using some API whereever possible(40K as compared to 10 megs sometimes).

I have cleaned up the most OCX and useless references there is. Actually, what's taking so much space is MDAC (about 8 megs) and I have 1mb of database file. I think there's an additionnal dao360.dll file somewhere and some others 300-400k file packaged. I might clean up some other OCX but this won't change my package size.

I'm still working on my problem but I'm beginning to think it's not that bad. My installation prompts the user to install mdac over and over, so what's the big deal, he'll run my install only once. I'm pretty sure now that's not the reason why my application doesn't start on win95.

See ya