>>More specifically, I have a large table (approx. 14 million records). I also have a smaller table (approx. 7000 records) that acts as a lookup table for other information. Ideally, I would just use a join but my queries then take nearly 2 days to run. I've found that if I just add the field, the run time drops to 1-2 hours. I need to add a field from the lookup table to the big table but I don't have enough room to just create another table. I would like to be able to add a field to the big table and update the information using the smaller table. I'm not a very advanced FoxPro user so any advice in this matter or how I have set things up would be greatly appreciated.
>
>You can use UPDATE, but firstly stop and look at your queries. Apparently, your database is not optimized, because there is no such Foxpro query which requires 2 days to run.

Vishni,

If you are not fully versed in it's concepts look up Rushmore Optimization in FoxPro's help. Generally speaking though, the best way to optimize your queries is to have an index tag on the table you are querying that matches as closely as possible to the FOR clause of your SQL-SELECT. Analyze your query and your tables to see where your FOR statement could be modified and/or index TAG's could be added to your tables CDX.

Hope this helps.