I've experienced this challeng as well. Using SQL select queries, you can modify selected records in the base table by modifying records in the base query. When joining two tables, however, both tables must be base tables. I have solved this problem by saving the query in a temporary directory, closing it and reopening it. I can then perform joins and updates as I please with it. Having done so, now I can join it with the original base table to update it. This will only work if you have a known primary key in the original base table, so that you will be able to perform this last update.
Blessings, Michael Hanna > -----Original Message----- > From: ALICIA COX [SMTP:[EMAIL PROTECTED]] > Sent: Friday, December 21, 2001 5:09 PM > To: [EMAIL PROTECTED] > Subject: MI-L Base Tables > > I want to know if there is a means to make a non-base table be treated > like a base table, for use in the SQL Queries (when using two tables, > Where <Table1>.Obj Within <Table1>.Obj, This seems to happen when > working from a table imported in from Microsoft excel or Access. I know > that I am probably ditzing with it being so close to X-mas, but this is > really stumping me. > > Alicia Kaye Cox > DHS / CH&P / PMSS > 535 W. Jefferson, 3rd Floor > Phone: 217 / 524 - 5987 > Fax: 217 / 557 - 0515 > [EMAIL PROTECTED] > > > > _______________________________________________________________________ > List hosting provided by Directions Magazine | www.directionsmag.com | > To unsubscribe, send e-mail to [EMAIL PROTECTED] and > put "unsubscribe MapInfo-L" in the message body. _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body.
