Autogenerated DataAccess.pas unit?

[aolson (Alan Olson)]

I’ve been messing around with writing a MacOS data abstract client. I do not use Relativity server, but a custom service hosted on one of our servers. When I created the macOS oxygene project, a dataaccess.pas unit was autocreated. is this for Relativity servers only? Is this a necessity, or more of a suggestion?

please explain how this is supposed to be used?

Thanks

[antonk]

It should be considered more as a code sample. Its purpose is to show how things like data access are done and to serve as a seed for the real application data access code.

[aolson (Alan Olson)]

Thanks. Could you help me with this question?

OSX Bindings vs. .NET bindings

I have written many apps in Oxygene for .NET/WPF and these apps have used Data Abstract for data access and bindings. I find the .NET binding logic easy to understand. I do a DALINQ query to return an array/list, and then I can simply set my grid’s ItemSource property to this list or array. The underlying XAML gives the field names for which to bind, and more. I am now trying to write my first MacOS app in Oxygene, again using Data Abstract. I have a few questions about binding that are con…

[mh (marc hoffman)]

ill handle that one, in the morning. )

[aolson (Alan Olson)]

Thanks marc!