Hi Joe,
Well, I didn't exactly suggested to completely ditch VO, but since that you have an app working and delivered in X# (and no more in VO), I think it makes sense to now start developing and updating it directly in X#, instead of continuing to make the code changes in VO first!
Regarding replacing the standard VO.* libraries (which are X# compiled libraries though, they are not VO ones) with their XSharp.VO* equivalents, I think it's still too early for you to do that now, especially since bBrowser does not support them (yet, hopefully). My suggestion is to first just get comfortable using the new environment and start making the regular code changes directly in it.
As for moving from DBF to SQL, moving first to the new system classes would help, but I don't think it's mandatory, after all there are so many VO apps that did the move long before X# was created anyway. But I'm not the best person to talk about SQL and conversion from DBF, will let the experts step in.
Best way to use Microsoft SQL database in X#
Re: Best way to use Microsoft SQL database in X#
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
Re: Best way to use Microsoft SQL database in X#
Hi Joe,
I think you are simply making a few steps in one.
As Chris suggested, you should first move your application from VO to X# using the "normal" classes for both RDD Classes and GUI classes (that means the classes without the XSharp. prefix).
And only if these are working, you should do the next step and think about SQL migration.
For the SQL migration, if you have a working DBF application and no or only little SQL experience, you should await the new X# product: the X# SQL RDD.
That should give you a similar API like the RDD Classes, but based on the ADO.NET and (different) SQL servers.
Robert has shown them in work on the Memmingen conference, and they should be ready early in 2024.
Wolfgang
I think you are simply making a few steps in one.
As Chris suggested, you should first move your application from VO to X# using the "normal" classes for both RDD Classes and GUI classes (that means the classes without the XSharp. prefix).
And only if these are working, you should do the next step and think about SQL migration.
For the SQL migration, if you have a working DBF application and no or only little SQL experience, you should await the new X# product: the X# SQL RDD.
That should give you a similar API like the RDD Classes, but based on the ADO.NET and (different) SQL servers.
Robert has shown them in work on the Memmingen conference, and they should be ready early in 2024.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Re: Best way to use Microsoft SQL database in X#
HI Wolfgang,
Just to be clear, Joe has already ported his app to X# long ago, he had just kept been using VO (since he's most familiar with this IDE) to update it since, instead of further developing it directly in X#/XIDE. His main goal now is to make the move from dbf to sql in this app.
Just to be clear, Joe has already ported his app to X# long ago, he had just kept been using VO (since he's most familiar with this IDE) to update it since, instead of further developing it directly in X#/XIDE. His main goal now is to make the move from dbf to sql in this app.
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
Re: Best way to use Microsoft SQL database in X#
Hi Chris,
I didn't knew that - thank you very much!
But nevertheless I think that for the migration of a DBF application to SQL the SQL RDD should be used - it should save a LOT of time. I think also that the logic of browse windows should be adapted to the SQL approach (with a limited view on large tables).
Moving a VOGUI based application to the XGUI classes is a lot of work, and if it should be done before bBwrowser for XGUI is released, then first all bBrowser based windows need to be rewritten.
My sample showed in Memmingen has only worked so well because it was developed with the migration in mind (so no bBrowser and browser windows, but only ListView based windows).
Wolfgang
I didn't knew that - thank you very much!
But nevertheless I think that for the migration of a DBF application to SQL the SQL RDD should be used - it should save a LOT of time. I think also that the logic of browse windows should be adapted to the SQL approach (with a limited view on large tables).
Moving a VOGUI based application to the XGUI classes is a lot of work, and if it should be done before bBwrowser for XGUI is released, then first all bBrowser based windows need to be rewritten.
My sample showed in Memmingen has only worked so well because it was developed with the migration in mind (so no bBrowser and browser windows, but only ListView based windows).
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it