Hello,
This is primarily related to the Excel/Word COM API and Microstation's VBA. I have some embedded excel and word OLE objects, I can detect them by scanning for cells, they show up under names such as "Microsoft Excel Worksheet". Is it possible to do something like this:
Dim xlWorkbook as Excel.Workbook
Set xlWorkbook = DetectedCell.AsExcelWorkbook
I'm sure the above doesn't exist, but is there a way to attach to that object?
Thanks.
Viktor_Kulik said:Is it possible to edit OLE object in MicroStation using COM Api?
Probably a better place to ask that question would be a Microsoft Forum. The technologies (OLE, VBA) belong to Microsoft.
Is there a way to programmatically get at an Excel OLE spreadsheet using, say, Word VBA? If you can't do that in a 100% Microsoft environment then there's no way you can do it in MicroStation.
Regards, Jon Summers LA Solutions
Yea, i thought the answer would be something along those lines. Thanks for your prompt answer either way.
Viktor_Kulik,
Are you Using OLE Containers (or considered using them) and asking how to perform: Read, Update and Delete operations on the ones stored in MicroStation DGN Files?
Thank you,Bob
That is correct. Any ideas?
I have a very raw MicroStation VBA Project from several years back primarily for CAD admins to perform UNC path updates/renames (NOTE: Server renames can be addressed simply by editing a client Windows .hosts file) and create a deliverable VBA API (procedural methods and classes), but I never got back to performing final QA on it. This project in my estimation is about 80% complete and could be modified/updated as a community project. The underlying code used a public documented "description" of the linkage format, though a public structure was never released. Therefore, this raw VBA example implementation could be migrated to other more modern language implementations like: e.g. C#, C/C++, etc. Let me give it a quick look and see if it is in this recalled "semi-useful" state and I can post to under our MicroStation CONNECT Code Examples and Utilities.
I will update this thread with the name and link if I can do so at this time (shortly).
HTH,Bob
FYi. I estimate about 2 or 3 hours (realistically spread across a couple days) work is needed to finish review and test of current enabled functionality.
Please "BUMP" this thread if you do not see another update by end of Monday 12/22.
FWIW. This code example is the only public way we can accomplish this type of modification since the structures are not published and not likely to be published or APIs made available - since MicroStation Tables and Reports are a path to replace this functionality going forward. It should be noted that this code project would also be the only way to parse and update/migrate/replace the old OLE/DDE functionality to MicroStation Tables and Reports too.