Microsoft Forms 2.0 Object Library Vb6
Siri
Please tell me shall download the missing references same with Office 2016, or I need to download other references specific for Office 365. (Like for Office 2016, the Microsoft Forms 2.0 Object Library reference which needed by my project is C:\Windows\System32\FM20.DLL, but for Office 365, I don't know is it the same. Do I still need Microsoft Forms 2.0 Object Library for Office 365? Or maybe what I need is Microsoft Forms 3.0 Object Library?)
Where you have problem with references, then onside this screen you 'll see "MISSING" i don't see up there.
Anyway, you can use early binding (as object) to make your code working any version, any path to rights controls.
Thank you for help.
I'm sorry my description is not clear. When I mentioned "Missing", I mean I cannot find the related files in my laptop, e.g., the Microsoft Forms 2.0 Object Library related file is C:\Windows\System32\FM20.DLL, but I can't find C:\Windows\System32\FM20.DLL in my laptop, so I need to download this reference, but I don't know shall I download the specific one for Office 365.
Yes, you mention missing as "I cant find" than my solution is - switch to Combobox
MF20 that is a general library ActiveX controls. So you can use it any time in any office.
CC1 that is a tool with enhanced AciveX like
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'People who live in windowed environments shouldn't cast pointers.'
RE: Don't use Microsoft Forms 2.0 Object Library! CCLINT (Programmer)29 Jul 03 10:10>I then found the following from Microsoft...
You should post the article number or address when posting something like this before scaring everyone.
There is no problem using/referencing it as I can see...just don't distribute it.
If it is not on the client's PC, the client can freely download the Microsoft ActiveX Control Pad which contains the Fm20.dll from the MS site...
Read this article:
=kb;en-us;224305
Because it is not supported under VB does not mean it will not work.
And because it is not supported it is only natural that it hasn't been tested.
You should test thoroughly anyways, know what is redistributable when distributing/selling, test any components like this which you rely the client to already have, etc, and read your EULA. RE: Don't use Microsoft Forms 2.0 Object Library! pokermat (Programmer)(OP)29 Jul 03 10:56johnwm - of course I saw this, I just didn't think it was a very professional solution. Here's the app, oh and by the way you'll have to download this thing from Microsoft.
CCLINT - patronising? I didn't say there was a problem referencing/using it, I said there was a problem installing it onto machines without Office. Hmmm, testing, didn't think of that.
Like I said, I was just trying to prevent others from making the same mistake. I guess I'll leave it to the 'Experts' in future. RE: Don't use Microsoft Forms 2.0 Object Library! CCLINT (Programmer)29 Jul 03 12:15>patronising
oh my goodness...
Nope. Do you feel that any corrections on mis-leading statements are a possible sign of patronizing?
>"I said there was a problem installing it onto machines without Office."
Not just that.
You said "Don't use..." in the subject title and in the first statement you said "...App on clients which don't have MS Office installed don't use the above library".
So the post, along with the quote, leads a person to believe that there is no work-around, and not possible unless they have MS office, when in the MS article you quoted clearly shows there is a solution.
And this offered solution you had left/cut out of the quote you posted for whatever reasons!
IMO, this was the problem.
Posting a reference, or at least the complete information, for something like this would have been alright then.
So, I was just trying to fill in the gaps and complete the mis-leading information!
RE: Don't use Microsoft Forms 2.0 Object Library! sdraper (Programmer)30 Jul 03 15:00pokermat,
CCLINT and johnwm have responded about 3000 times each to others posts. They have helped many, many people since they have been here. They were only trying to help in this case as well. So I don't think that two peeps that have helped so many would just jump in and try to bust yer chops. If you would have searched the forums for posts about the forms 2.0 library you probably would find that this subject has been discussed into the ground. So anyway thanks for contributing but don't take this all so personnally.
yer cyberpal, Sam
googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.
If you use the objects in other applications as part of your Visual Basic application, you may want to establish a reference to the object libraries of those applications. Before you can do that, you must first be sure that the application provides an object library.
The References dialog box shows all object libraries registered with the operating system. Scroll through the list for the application whose object library you want to reference. If the application isn't listed, you can use the Browse button to search for object libraries (*.olb and *.tlb) or executable files (*.exe and *.dll on Windows). References whose check boxes are selected are used by your project; those that aren't selected are not used, but can be added.
Select the object library reference in the Available References box in the References dialog box and choose OK. Your Visual Basic project now has a reference to the application's object library. If you open the Object Browser (press F2) and select the application's library, it displays the objects provided by the selected object library, as well as each object's methods and properties.
In the Object Browser, you can select a class in the Classes box and select a method or property in the Members box. Use copy and paste to add the syntax to your code.
These commands for importing user forms used to work fine. The path really does have those forms in it, however IS switched me to Terminal Server 2003. My security is set to "Trust access to Visual Basic Project", so that is not the problem in this case. The error message tells me to go to the log to see the problem, and it says the form is in use so it can't be imported. However I don't have the form open, and the import used to work with this exact code.
Perhaps my library references got re-set when they changed me to Terminal Server 2003. These are the ones that are checked off:
Visual Basic for Applications
Microsoft Excel 11.0 Object Library
OLE Automation
Microsoft Office 11.0 Object Library
Microsoft Forms 2.0 Object Library
Microsoft Outlook 11.0 Object Library
Microsoft Office Outlook View Control
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Word 11.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.0 Library
[SIZE="2"][center]Merge Or Convert Excel Trading Add-ins For Excel Convert Excel Into Web Pages Convert Databases Including Excel Business Spreadsheets Build Automatic Trading Models in Excel [/SIZE][/center]
I tried skipping over the userform import commands to see what happened, and, and the code following them started acting on the template workbook instead of the new one. ...and yes, the template did have all my userforms already in it. So that's why it wouldn't import them,... as you suggested they are already there.
So now I go to work to try and figure out why it's working on my template instead of the new book. So curious, because I didn't change anything... but now I know where to be looking in order to solve my new problem.
The reason why I didn't do Save As is because there were several sheets and modules that I didn't want in the new one. I solved the problem by setting up a variable for the name of the new workbook...
The Oracle Forms to XML conversion tool, Forms2XML was introduced in Oracle9i Oracle Developer Suite and is also available in Oracle Developer Suite 10g. This tool should also work on files from earlier releases of Oracle Forms. If the Oracle Forms to XML Conversion tool does not work for a specific file from an earlier version of Oracle Forms, then you must upgrade the file to Oracle Developer Suite 9i or 10g and then convert to XML
Forms2XML produces an XML file that has the same base name as the Forms file with an .xml extension. The extension _fmb, _mmb, or _olb is added to the base file name to indicate whether the original file was a Forms Modules, a MenuModule, or an Object Library. The following table displays a few examples of the changes the tool makes to the name of the file being converted:
The Forms2XML command takes one or more Forms Module files as an argument. The files can be FormsModule (.fmb), ObjectLibrary (.olb), or MenuModule (.mmb) files. The output is placed in the current folder. The command has the following syntax:
93ddb68554