Convert to SQL Library Download

Das Goravani goravanis at
Fri Apr 16 17:26:53 UTC 2021

The link for my convert to SQL tool is


Please note that the tool contains one button which “lower cases your field names”… this is not necessary, you can go with field names being any case

If you change them you may have trouble going back to your DF1 should you need to

I changed mine and I changed my DF1 at the same time so that worked out

Skip the lowercasing step if you are happy with your field names as they are

Read all the notes on the window the library includes.. ask me questions if you have any.. I dont mind helping, really I dont

My system relies on File Formats names matching your table class names and your database tables names in this way:

File Format Name is exactly name of corresponding database table, this happens automatically if you let it

Schemas need to be the same as file formats but start with an S instead of an F

Do not use the buttons for making queries.. you dont need them

There are two buttons that you dont need, I forget the other one right now

One of the buttons makes task variable rows for all your file classes, you need this, but besides all the row variables that button creates you need to create 2 on your own and they need to be named

tvLastRowUsed. (Char 30 say)
tvLastFileUsed.  (Char 30)

There is a routine that needs to be in your startup task that isn’t in the library, I will have to provide it to you in an email.. it makes INSERTs work in SQLite

The Omnis routine for making a Database from a DF1 is under Add Ons and says “Convert Datafile to RDBMS”, Juan asked where it is I believe. 

I want to help if I can, I like writing emails, I dont mind helping.. just no grief is all.. not able to handle that.

To understand all that SQL and Omnis do when working together takes some time, be patient, ask questions, I and others will help for sure. 

When you get the library and use it keep in mind that the code routines in the object and then table master class have been gone over a lot, written carefully, debugged, and are working in the field.. you may see little things in them that could be improved or different.. BE CAREFUL.. you might break something that is working.. with that said the person who has used my stuff successfully has changed some of the routines to his benefit.  There are other ways to do things I do in them. 

I’m honored if others use this and especially if they take it all the way to up and running in SQL.. I think of myself as intermediate, not an advanced developer.. so I’m tickled that I can help at all.. help others as this list has SO helped me over the years esp. with my SQL conversion about a year ago.. I asked a LOT of questions and everybody was so good about it all. 

There is no “Previous” command in SQL.. if you use Previous you’ll have to re code those areas. SQL works super fast with lists.. usually on “Previous” it’s really like going to a previous line in a list.. and that’s how you recode it usually.. is you make a list and work from that, moving up and down your records rather than Nexting through them. 

SQL is so slick.. SQLIte works great too.. once you move to SQL you’ll never look back. 

Places in your app where you do repeat loops that do a lot of processing.. right now you have possibly Find and Next to move through the records.. those will work with my stuff.. but it will be a little slow due to the overhead of putting the SQL row into the CRB.. and taking the CRB and putting it into the SQL row.. so you will likely re write these areas to be more correctly SQL.. again where you work with a list most likely.. you will find that you are able to speed things up with SQL.. it’s very fast. When you want total speed there are ways to maximize it’s possibility.. in SQL and Omnis.. in those key areas you will likely do a little more work than just my conversions process. 

I’m jazzed two people are now interested, I look forward to helping if I can

Be prepared to do the conversion a few times.. you will likely encounter things you wish you did differently, and will go back and start over again.. be prepared that you may start over a few times.

The person who has made it through this successfully, I’m not outing him because that’s up to him.. if he outs himself in this regard maybe he could answer things too.. he’s better than me at SQL and possibly Omnis too. 

Thanks and best of luck.. write and ask questions if unsure about anything.. 

Das Goravani

More information about the omnisdev-en mailing list