General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
I'll give that a shot.
Thanks,
Michelle
>I have the same problem with SBT. I created a VFP database that contains views of the SBT data. For example, lv_armast is a view of the ArMast table, while lv_arymst is a view of the ArYmst table. I use these base views to create views that are UNIONs of the base views. For example, lv_armastunion is a UNION of the lv_armast and lv_arymst views.
>
>>In SBT, for some asinine reason known only to them, they split their data into current and history tables. These tables are identical in structure and just have a slightly different name.
>>
>>The reports I'm writing rely on data that can be either current or historical. So I have to deal with both tables.
>>
>>What I've been doing is using an SQL UNION to join the two tables into a third and working with that. Unfortunately, since the client has cleaned out their data since '94, this process takes forever on my 433. On their 166s, I can imagine it will just scream.
>>
>>Is there a better way to deal with this? The FoxFire reports can handle it without hardly a pause so there must be some way. Not being privy to the ways of FoxFire, I thought I'd ask here.
>>
>>Thanks,
>>
>>Michelle
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only