I use VB to write a DLL, mainly in the FORM of OLE embedded in EXCEL FORM, is to want to achieve through an external trigger the DLL, and then open the FORM, by OLE loaded a EXCEL file, implementation in the FORM above to change the edit operation, (operating results do not save to source the EXCEL file, through the corresponding API uploaded to the server database, EXCEL file only as a carrier of the template)
Then when the program debugging, completely no problem, function perfect, can realize the FORM inside the inside of the OLE EXCEL editor, and through the FORM of add a button to achieve EXCEL sheet,
But when I finished the debugging will be compiled into a DLL file, after registration, the same operation, after the open Form, OLE EXCEL part of the window, in the change after finished the first cell (literally change which cell), the keyboard, press enter, or select other cells, EXCEL part will be stuck, but the other buttons on the Form, including EXCEL SHEET page button can also be used, can realize SHEET page,,,, is the inside of the OLE EXCEL is dead, can't edit the,,,, an error message is "source application is busy, objects, no response"
But when debugging is fine,,,,,,,
CodePudding user response:
OLE seldom used (mainly difficult operation...
) Now that use the DLL, why not directly into Com add-in?
VB -- -- -- -- -- -- -- -- -- -- - new add-ons...