Have you thought about using a DBMS link to the text table and just refreshing the MI table. I actually use this technique for a similar scenario. Then we can get into the limitations of the microsoft ODBC drivers and the default field definitions imposed... but maybe you don't have time as an attribute, or how MI overwrites the tab file each time the text file is refreshed, but it is quite easy and powerful.
R
On Wed, 12 Nov 2003 11:30:53 +1100, Peter Zyczynski <[EMAIL PROTECTED]> wrote:
It's part of a transaction processing routine.--
Transactions (attribute edits) are stored in a text file rather than the underlying MI table (don't ask why, take too long to explain). Once the transactions are complete, this routine is run to apply the transactions back into the MI table.
Robert Crossley Agtrix P/L 9 Short St New Brighton 2483 Far Southern Queensland AUSTRALIA
153.549004 E 28.517344 S
P: 02 6680 1309 F: New Connection M: 0419 718 642 E: [EMAIL PROTECTED] W: www.agtrix.com W: www.wotzhere.com
--------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 9117
