xsharp.eu

In the RoadMap which listed the xSharp RDD and last bullet has:

What do you need ?

Aside from ADS, I am just wondering if will be possible to create something like ApolloDB to write to SQL-92 query syntax directly access data via an ADO.NET Data Provider.

Such a feature will enable us to return DataSet objects that can be bound to native Grid in WinForm/WPF or to third components data grids like Telerik, DevExpress and so on.

Hi Jamal,

that would be a project on its own.... it would be great to have something like this, but first the X# team needs time to finish the runtime and the RDD itself.

Of course I like this idea because it would really make a bridge between our DBF data and the SQL world!

Wolfgang

Jamal,
That is a great ide. But we could use some more information. What is it exactly that you would expect from this:

- SQL syntax to query DBF data (Advantage RDD allows that already)
- a DotNet provider linked to RDD workareas that uses filters and scoping like normal DBFs
- Should there be an automatic write back of changes to the DBFs?
- And should that to happen immediately (like normal DBFs) or should the changes be cached in the in memory dataset and its data tables and then written after all the changes are committed.

Robert

Hi Robert,

>> SQL syntax to query DBF data (Advantage RDD allows that already) <<

SAP lately based on what I hear has very bad support <g> and may too expensive.

>> a DotNet provider linked to RDD workareas that uses filters and scoping like normal DBFs <<

Yes, but using SQL commands.

>> Should there be an automatic write back of changes to the DBFs? <<
- And should that to happen immediately (like normal DBFs) or should the changes be cached in the in memory dataset and its data tables and then written after all the changes are committed. <<

That would depend on the supporting grid component or if the data is shown in data-aware form or not.

Maybe you guys look at apollodb.com or talk to them to see how their technology could be utilized in xSharp.

Jamal

Hi Robert,

and I think that this could be a commercial component.

Wolfgang

Jamal,

We will have a look at ApolloDB. From what I read their product already supports Ado.NET and VS 2017. So nothing stops you from using Apollo with X# already and you should be able to use it with both Windows Forms as well as WPF.

I am not sure what you are asking for exactly. Is ApolloDB not sufficient for what you need or are you asking us to create an ApolloDB "clone" ?

Robert

Hi Robert,

I've given ApolloDB a short look, and it looks interesting.

Since the developers had made the Six driver that was used in Clipper 5.2 by CA, they should have enough experience with DBFs, but as I remember the DBFFPT from Clipper 5.3 (Comix) was stabler than the Six version of 5.2 - but things could have changed.

IMHO it makes not much sense to rebuild functionality already present in another product, but it would be interesting to join forces, so maybe a common RDD could be built.

The ApolloDB product seems to be in development - last update was in January, but I was not able to find any statement from a current ApolloDB user.

Maybe they are interested in any sort of collaboration to open up a new market for their server.

Wolfgang

Hi Robert,

The ApolloDB is not 100% compatible with the VO DBFCDX RDD specifications since VO added long field lengths above 1023 characters, see: http://www.apollodb.com/apollo_engine.asp#t4

In VO I can specify 3000 characters field with no issues (no memo field needed).

So, maybe a clone component would be ideal.

Jamal

It would be very interesting. ADS is as dead as VO, meaning we can still use it but there is no support from SAP nor a chance that we will spend clients money on it. SAP even didn't show the courtesy to keep the forum alive, after first shutting down the original and helpful forum.

Basically if you could replace ADS (and charge for that) there may be a potential source of income. But that won't be an overnight job I am afraid. For the short term you should take a look at ADS Data Architect. I can just use standard ADS to both query and fill DBF files. We use it for exchanging data via WPF; everything we change in any designated database we automatically create a query for which is appended to a MySQL database using WPF. Any user set up to receive these queries read them, again using WPF, and ADS (even ADS local server) allows us to execute the queries 1:1 onto the DBF files of the receiver, something which would be a lot more difficult to realize without ADS.

It works actually quite flawless.

Dick

Hi Dick,

ADS is not dead as VO: SAP is alive and probably will not close the next years, and they continue to sell it, and if some new OS requires it, they will do the needed changes. Even the support is alive - not very well, and for sure not fast, but there is someone that supports it.

I don't know what the ApolloDB people is doing and how many licences they sell, but they have a working product, and I hope they are so smart to collaborate in some manner. It is time to join forces, and why redevelop something from scratch if there is something that is already done.

Robert and his group has a lot to do, and it will take some time until they will have the time to dedicate it to this project. I would like such a product, and I'm sure our "gang of four" is be able to develop a fantastic thing, but their time is limited and a lot is to do for X#.

Maybe Robert can find an agreement with the ApolloDB people for a native X# RDD, and a SQL engine that is to pay (after all, we all need to live from our work).

The limits that the engine already has like the maximum string field should be easy to change ( but I have to say that I have no table with such a large field ).

Wolfgang