Last time, I figured out how to make The Dummy Table Technique work. Using this technique is a bit different than when using it with full blown SQL (i.e., the kind with a dedicated engine). Not only do I need to declare the dummy table in my dictionary but I have to ensure that the SQLite table physically exists.
So, then, what happens if my initial dictionary specification for my Dummy file:
...
What happens when I change the dictionary and remake the app and open it? ErrorCode() 47 of course. Except that SQLite is quite not quite friendly enough to tell me that in the way I'm used to:
...
Truth? That's hard. It means checking every filter, every totaling op, everything to determine the number of variables and data types and number of variables per data type that I need. Then I have to accurately guess what I may be asked for in the future.
I could “just” declare a bunch of CStrings and let Clarion convert data for me. Of course, any numeric is quite likely to need to be FORMATted so that leading/trailing zeros are where they're expected to be.
...
The only issue I had with this is that it didn't work. Both
Access:DUMMY.Open
and
Relate:DUMMY.Open
returned the error window shown in Figure 1.
...
This works fine. The final CLOSE is not actually necessary, if there was an error, the file wasn't OPENed, that's why there was an error. But, if there wasn't an error, the CLOSE is necessary. It probably should be wrapped in some conditional code.
The standard template-generated opening of the file will create it. So, everything is copacetic.
...