FM20.DLL included unnecessarily ? 3

[boggg1]

In my mad rush to convert my Access-based database analysis tool (in Access Visual Basic) to "full" Visual Basic I made mistakes - well there's a surprise. When I prepare the converted project for packaging I see a reference to FM20.DLL which (if my understanding is right) should only occur within Office applications and should not be distributed (Microsoft licensing restriction) with "full" Visual Basic. I want this application to run stand-alone on Office-less PC's (indeed the very reason why I am converting to Visual Basic). Looking at References and Components I cannot find any object which requires FM20.DLL and I have worked through many of the objects manually using Object Browser and positively identified them as "full" Visual Basic components (not part of FM20.DLL) using the list of properties which are exposed. Unfortunately I have used someone else's (very useful) code within my project (a possible source of the mysterious link) but I have consistantly failed to identify why FM20.DLL is necessary.

Can I identify what part of my system (what control ?) is using FM20.DLL so I can eliminate it ?

Boggg1


Can

 

[DrJavaJoe]

My first thought would be to open the .frm files in notepad and if you see a reference at the top to fm20.dll, something like:

Object = "{0D452EE1-E08F-101A-852E-02608C4D0BB4}#2.0#0"; "FM20.DLL"

Then search for MSForms and you should find the control that is giving you the problem.



"Two strings walk into a bar. The first string says to the bartender: 'Bartender, I'll have a beer. u.5n$x5t?*&4ru!2[sACC~ErJ'. The second string says: 'Pardon my friend, he isn't NULL terminated'."

 

[johnwm]

Here is the MS solution:

http://support.microsoft.com/default.aspx?kbid=224305

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first

'If we're supposed to work in Hex, why have we only got A fingers?'