In the past week I have made extensive tests using the Active link feature against MS SQL 2005 Express Databases (Maybe the most common Database from the MS stable in use today in Home Development and Small Business environments). Using the wizards I went for the �all or nothing� approach of automatically selecting all columns in the required table, where needed I supplied a surrogate primary key based on a Numeric Type field. Due to fact that my remote tables contain non-English character types I had to make a named browse as the default browse (As in all A5 versions) returns a data array displaying non-English character sets as gibberish. Using this browse I set about updating �on the fly� data values. Even the most basic edit upon committing to save would result in a painful 3.5 minute wait until the sql action involved committed itself and returned control to the open browse. Fearing this to be an issue regarding language compatibility I began reverse engineering of the data and data structures involved.
After �burnin the midnight oil� all week I have come to the conclusion (Based on previous experience using MS data engines )that, the culprit has nothing to do with character sets and data set page collation issues. I omitted from the active link definition the �*� (all) select and included only Numeric and Character type fields from the remote table (previous selection included Time type columns).
Building a named browse from the resulting active link table and then opening in edit mode I can very happily report that the commit action (F9) is instantaneous, less than 0.03 secs even on a busy server.
Now that�s over with I can get do to some serious testing with mapped tables based on two active link tables, so as to result in a single point of data entry for my application currently under development.
P.S. Alpha works with non-english character sets at the same level as most IDE non localised software, you just have to look beyond the basics so as to achieve the required result.
After �burnin the midnight oil� all week I have come to the conclusion (Based on previous experience using MS data engines )that, the culprit has nothing to do with character sets and data set page collation issues. I omitted from the active link definition the �*� (all) select and included only Numeric and Character type fields from the remote table (previous selection included Time type columns).
Building a named browse from the resulting active link table and then opening in edit mode I can very happily report that the commit action (F9) is instantaneous, less than 0.03 secs even on a busy server.
Now that�s over with I can get do to some serious testing with mapped tables based on two active link tables, so as to result in a single point of data entry for my application currently under development.
P.S. Alpha works with non-english character sets at the same level as most IDE non localised software, you just have to look beyond the basics so as to achieve the required result.
Comment