Approaching Omnis again scares me, too much to learn?
I agree the recommended way to use schema and table classes is way too complex for me.
But you can still do it the Omnis 7 way using handy file classes and send your sql statements to the new multi instances v3 Dam.
Learn something new every day!
> On 5 Jan 2018, at 19:09, Jerry Greenberg <email@example.com> wrote:
> I loved the dml and I fought going from dml to sql tooth and nail, but when I started working on larger corporate projects I had no choice. Like I said previously basic sql is pretty easy to learn, it’s when you get into large sql scripts, transactions, etc. that it gets a bit complicated. But you can avoid much of that complication by using a combination of basic sql and Omnis (smaller projects), but once again it’s not the most efficient or accepted way of doing things.
> I still say that it’s when you get into extra layers like table classes, and queries classes that things start to look a little crazy to the new sql programmers. There are great advantages to their use in larger multi developer environments, but in smaller environments they add a lot of complexity. The simple fact that if you have 100 server tables, then 100 schema, then you add 100 table classes, and possibly that many or more query classes makes you want to scratch your head. Plus many if not most clients seem to keep their sql separate, on the backend, stored procedures etc.
> just my .01 worth
> At 08:37 AM 1/5/2018, you wrote:
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com