Upgraded my workstation to Windows 10, so VB6 is no longer an option for my PC-DMIS software efforts.
I've got Visual Studio 2107 now, and I've run into a problem using PC-DMIS collections. In a nutshell, vb6 .net doesn't recognize them as collections. I have to declare the PC-DMIS application as "Object" in order to be able to enumerate through the collections. I was told that this means it's doing "late binding" - who cares. I need intellisense because I'm a terrible typist. In the screenshot below, if I change the declaration of the "app" variable to type "Object", the compile error goes away, and the code runs fine. But I don't see this as a solution.
I'll also point out that the Microsoft's File System Object collections work just fine when used in the same manner.
Unfortunately I haven't done *any* work in VB.NET (I use the superb Delphi (Pascal) environment when not programming PC-DMIS Basic, Excel or other exotic languages). Actually, I haven't done anything .NET...
I believe a collection must implement a certain interface/iterator to have "for each" to work - it looks like PC-DMIS is not doing it (or exporting it) in exactly the right way.
If it "just works" with an added iterator, your chance for errors will be quite small, just verify that the iterator works, and then copy it into all the programs.
As for Pascal, I don't think there's any free Delphi, but the FreePascal with Lazarus IDE is completely free, and almost the same as Delphi (
https://www.lazarus-ide.org/). Quite a big leap from Turbo Pascal, though, with all this fancy Object Orientation...
If it "just works" with an added iterator, your chance for errors will be quite small, just verify that the iterator works, and then copy it into all the programs.
As for Pascal, I don't think there's any free Delphi, but the FreePascal with Lazarus IDE is completely free, and almost the same as Delphi (
https://www.lazarus-ide.org/). Quite a big leap from Turbo Pascal, though, with all this fancy Object Orientation...