Help with "dll" files.

  • Thread starter Thread starter FatMan
  • Start date Start date
F

FatMan

Hi all:
I created a little database program and have packedaged it including access
runtime using my "developer eddition" of Access 2000. It is running on
Win2000, WinXp (Home & Pro), and Vista without problems. One person has
tried to install it on a Win98 (not sure of the version or how up to date it
is) and now recives error messages regarding OLEAUT32.dll (file can not
start) and MSOERES.dll (file can not be found). The error messages appeared
after the person installed my database program. I have checked and both
files are included in my install package.

Can anyone offer any ideas as to how to fix this problem?

Thanks,
FatMan
 
Chris:
Thanks for the help.

To be honest I not sure how many dlls got added/changed due to my package.
I only mentioned the two because that is what the person mentioned to me. He
is not even sure if he is running Win95 or Win98.

As to way these were updated/changed I am not sure why. All I did was run
the package tool and accept the defaults. Not even sure why it would want
anything to deal with Outlook Express as my database doesn't have any email
functionality.

Some of the other sites I have looked at have suggested extracting the dlls
from the CAB files on the install CD. I think I might give that a go and if
that fails tell him to reinstall his operating system. Which will be a neat
trick since he most likely doesn't know what an operation system is. What
really ticks me off about this is that he claims he has had a new computer
for 6 months and just has not unpacked it yet. If he had we would not be in
this problem....GRRRRRR.

Is there general rules of thumb to follow to know what other versions of
windows dlls are compatible with mine. I am on WinXP Pro.

Thanks,
FatMan
 
FatMan said:
I created a little database program and have packedaged it including access
runtime using my "developer eddition" of Access 2000. It is running on
Win2000, WinXp (Home & Pro), and Vista without problems. One person has
tried to install it on a Win98 (not sure of the version or how up to date it
is) and now recives error messages regarding OLEAUT32.dll (file can not
start) and MSOERES.dll (file can not be found). The error messages appeared
after the person installed my database program. I have checked and both
files are included in my install package.
Click to expand...

Ouch. I recall the A2000 runtime did wield things. Did you download
the minimal version of it which didn't include IE5.0?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q243957

Also one rule is to build the runtime in the oldest version of the OS
you want to support. That way if it does grab any system DLLs
they'll be older than most of your clients. I don't think this rule
applies to the A2000 minimum runtime or to newer runtimes as they
don't attempt to replace any system DLLs. However I can't be sure
about that as I haven't taken a good close look at this for quite some
time.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Tony:
If I was to move up to Access 2007 would the chance of having this type of
problem decrease? I have been told that the run time for Access 2007 is free
for distribution. Is this correct? If my database program runs in Access
2000 is it safe to assume that it should run in Access 2007 with out a
problem?

Thanks,
FatMan
 
Chris:
Thanks for the words of advice. We were able to just replace the two dlls
in question and had no athoer problems. Guess we got lucky. Don't get me
wrong I didn't blame the owner of the computer for the problem but accepted
full responsibility and felt lower than whale poo for it. Just fraustrated
that if he was using the new computer it never would have been an issue. Of
the 50 or so using the application on their computers he is the ONLY one I
have heard this problem from....not his fault....my fault but just
fraustrating knowing it could have been prevented.

I will ask you the same quesiton I asked Tony who posted a response to my
question if you don't mind answering:

If I was to move up to Access 2007 would the chance of having this type of
problem decrease? I have been told that the run time for Access 2007 is free
for distribution. Is this correct? If my database program runs in Access
2000 is it safe to assume that it should run in Access 2007 with out a
problem?

Thanks,
FatMan
 
FatMan said:
If I was to move up to Access 2007 would the chance of having this type of
problem decrease? I have been told that the run time for Access 2007 is free
for distribution. Is this correct?
Click to expand...

Yes. Also see Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm
If my database program runs in Access
2000 is it safe to assume that it should run in Access 2007 with out a
problem?
Click to expand...

No. There are little quirks you have to be aware of especially if
Microsoft has tightened up the behavior of some things. Allen Browne
has a page on these quirks. www.allenbrowne.com. But once you're
past the quirks it won't be too bad.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
If I was to move up to Access 2007 would the chance of having this
type of problem decrease? I have been told that the run time for
Access 2007 is free for distribution. Is this correct? If my
database program runs in Access 2000 is it safe to assume that it
should run in Access 2007 with out a problem?
Click to expand...

But if you use the A2K7 runtime, you won't be able to deploy any any
version of Windows before WinXP.
 
Back
Top