T
Thomas Mercer-Hursh
Guest
I am currently modifying ABL2DB to use Proparse to assist in relating a buffer name to a DB table name as follows: In BuildTableLinks.cls, as each compile unit comes up for analysis, I use Proparse to find all the define buffer statements and create a lookup table which has the buffer name, table name, and whether or not the table is a DB or temp-table. Then, as I encounter buffer references in the XREF, I will be looking them up and building the link for any DB tables. Now, there are a couple of other things I could be doing, but am not presently intending to do, so I'd like to through them out and see if people think they have any value. One, I could be building database table(s) of temp-table definitions - potentially table, field, and index just like there is for DB tables. Two, I could be building links between compile units and these temp-table definitions, just like I do for DB tables. Three, I could be creating a database table of buffer names for DB tables with links to the table. Four, that table could also link buffer names to temp-tables. Note that one might think of making the buffer name a property of the link between compile unit and db table except that more than one buffer name might be used in a compile unit, so it would have to be part of the index. I am not immediately moved to do this since it seems to me that buffer naming can be pretty arbitrary and temp-tables, unlike DB tables, are local implementation artifacts, not something potentially shared across the application. So, let me know what you think.
Continue reading...
Continue reading...