Kurt Wendt wrote on 2015-10-20: > So - today at work when I compiled this app - I noticed that VFP was generating these files w/VBR & TLB extensions. I was Quite surprised by this - as I don't remember seeing these files before. And, I did a Google search - but, some of the results were confusing and seemingly conflicting - such as this one programmer forum where a person asked: > "BUILD EXE why no .vbr and .tlb files?" > ...and one response they got was: > "You're thinking of VB. Make sure you are connected to the correct Help. VFP does not use those extensions. " > While another person responded: > "VFP will only create those extensions for an .EXE if you have an OLEPublic class in your project. " > I know there is some Office Automation in this App having to do with Excel files - and maybe THAT is why these files are generated. Am I right? > > Regards, > Kurt Wendt > Consultant >
Kurt, The "OLEPublic" is the cause. If you do not automate the VFP executable this flag is not needed. When you drag an interface from the Object Browser to a PRG, it will add that flag. I usually delete them. When building a project that has a class flagged as OLEPublic, VFP is required to be in Administrative mode. It updates the registry during the build to update the flags. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
