I've created an ActiveX DLL, wich defines an object type to EDI with
one of my systems. This component offer many methods and properties to
allow the user to fill all the information on the object and then write
a file to be sent according to my specs, using one of it's methods.

The file reading process is also handled by a method of the component,
wich returns a collection of the same object type, read fm the file.

Everything is working perfectly, was exaustively tested and works
exactly as expected, but I still can't distribute it to my
collaborators because it's not behaving the same way as my machine!

I've tested it on 3 different machines. Two of them worked fine. On the
3rd one, the file was created, but the information was not stored in it!

My machine has VB 6.0 (fix #4) installed. The others don't (I used a
package created in VB pkg mngr for distribtn). All the 3 machines are
Win95.

The component was originally designed using a FileSystemObject to
create the file, replaced later by simple Write # and Input #
statements. The behavior (in fact, the problem) was the same.

What is missing? I suspect there's any base DLL I must upgrade. I have
to know what it is to recomment upgrade on my collaborators!

If anybody has a hint for me, I wud be really glad to see it.

Tks for any news.
--
Ivan Daudt

I hope this will help

Jean,

Many tks for yr feedback.

Just to explain some of yr items:
- No, I'm not using ADO or any database engine to write my files.
They're pure ASCII files. The problem I was having was because the file
recorded was empty!

I used the class FileSystemObject to create my file. This class depends
of the Scripting class to work, where I believe was the problem.
My component needs those classes, but the interface doesn't and VB was
not identifying it as part of the dependency, exactly as U assumed.

Anywhay, I discovered that everything works perfectly if the user
installs I.E. 5.x. Believe because I.E. also updates some parts of the
Windows kernel and add many new components to the system by itself.

Some of them may match with VB's components, and then my app works well
when IE 5.x is installed.

Guess what? When I distribute the app & my component, I warn our
collaborators that it needs IE 5.x to work! And everyone becomes
happy! :-)

Hope it help somebody else, before they leave VB...

Happy new year/century/millenium for us all!
Ivan Daudt