Search found 113 matches
- Thu Oct 17, 2024 3:28 pm
- Forum: 3rd party products
- Topic: Convert AdoRecordSet to DataTable
- Replies: 3
- Views: 659
Re: Convert AdoRecordSet to DataTable
Hi Robert, In your example, on this line: foreach oField as AdoField in oRs:Fields I get this error: Error XS1579 foreach statement cannot operate on variables of type 'Xs2Ado.AdoFields' because 'Xs2Ado.AdoFields' does not contain a public instance or extension definition for 'GetEnumerator' How do ...
- Fri Sep 13, 2024 6:50 am
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 61
- Views: 6248
Re: Miscellaneous questions about converting VO code to X#
Hi Chris, Thank you very much for your reply. Using NEW is indeed the answer, now that you mentioned this I looked at the "Class hierarchy modifiers" page in the online documentation again and it is explained there. I did see this page yesterday but I did not read it carefully because there was so ...
- Thu Sep 12, 2024 2:36 pm
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 61
- Views: 6248
Re: Miscellaneous questions about converting VO code to X#
Ok, so nobody knows an answer to the previous question unfortunately. Next question. The System.Windows.Forms.Form class has a method Close(). How can I override this method without getting the warning "Warning XS0108 'MyClass.Close()' hides inherited member 'System.Windows.Forms.Form.Close()'. Use ...
- Wed Sep 11, 2024 1:03 pm
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 61
- Views: 6248
Re: Miscellaneous questions about converting VO code to X#
While converting a VO.DataDialog to a System.Windows.Forms.Form I ran into some problems, maybe because the whole setup is not straightforward. In the VO code, it starts with a class that has a lot of "helper" methods, this class inherits from VO.DataDialog.Then there is a second class with another ...
- Mon Sep 09, 2024 10:07 am
- Forum: Product
- Topic: Best solutions for converting known/often used VO libs to X#?
- Replies: 24
- Views: 5136
Re: Best solutions for converting known/often used VO libs to X#?
of course bBrowser need to be adapted to these classes to work. If this adaption is made, does not depends on me, but on Joachim Bieler and the X# development team. Of course as bBrowser user I'm highly interested in this project (but I have to confess that I'm using more and more ListViews instead ...
- Mon Sep 09, 2024 7:24 am
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 61
- Views: 6248
Re: Miscellaneous questions about converting VO code to X#
Hi Wolfgang and Chris, Thank you for your replies. If I understand you correctly, then: - XGUI replaces VOGUI which means that all windows have to be changed at once, I can't do it one by one. - I would need a new version of bBrowser which does not exist yet. This makes it impossible to start using ...
- Fri Sep 06, 2024 6:53 pm
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 61
- Views: 6248
Re: Miscellaneous questions about converting VO code to X#
The VO windows have been converted to VO-forms in X#, with the help of the VOXPorter, and they work. Now I would like to transform them one by one to Winforms. I could try to use the Winforms versions also created by the VOXPorter but as I understand it only the layout is converted, not the logic ...
- Tue Jul 16, 2024 3:17 pm
- Forum: Product
- Topic: VO.WCError
- Replies: 10
- Views: 1001
Re: VO.WCError
Hi Chris, They are all created together at once, that is why I add them all together at once ;) I do not change any of the 3 components individually, I just add all 3 together (meaning I select them all 3 together in the Add -> Existing Item dialog). Anyway, I found that doing a Clean Solution after ...
- Tue Jul 16, 2024 1:33 pm
- Forum: Product
- Topic: VO.WCError
- Replies: 10
- Views: 1001
Re: VO.WCError
Hi Kees, Ouch, adding existing windows this way is really pushing it, those are meant to be "one" entity. Chris, Just wondering, why is this way of adding "really pushing it" and what do you mean by that it should be one entity? The code for a window is always split in 3 files I think. Kees.
- Tue Jul 16, 2024 12:50 pm
- Forum: Product
- Topic: VO.WCError
- Replies: 10
- Views: 1001
Re: VO.WCError
Hi Chris, Most of the projects would still contain too much code to import in one go I think. Also, the projects are all dependent on each other because the windows, the classes, inheritances and code are not placed together in a sensible way but scattered all over. The approach I took was to begin ...