At 01:49 PM 3/24/2008 -0400, David Boatright wrote: > >Charlie Coleman [mailto:[EMAIL PROTECTED] > > >For all practical purposes doing a USE <table>.... does not bring down the > >whole table. The only exceptions I've seen to this is where the total table > >size was small. I can't remember what the cutoff was. Maybe 64k? Even then, > >since it's so small it's not really noticed. But my gigabyte-size tables > >open in blip of time over a 100Mbps network. > >-Charlie > >Hmmmm I created a blank form and dropped two tables into the data >enviroment. One table has about 2000 records and the other about 3000 >records. It took 15 seconds for the form to open on the clients network
Are you joining those 2 tables in some way? I don't use Views because I don't like the loss of control. Plus SQL syntax just isn't good for a lot of situations - and that's all a View really is: a SQL statement (albeit with some other under-the-hood stuff to send updates back to the database). When I use VFP tables, I issue the USE commands myself and I have my own code (classes, etc) build data cursors if I need them. So if you're doing something in the DE that pertains to SQL, you may indeed be bringing down the whole table - and the same thing would happen no matter what back end you were using - SQL Server, MySQL, PostgreSQL, etc. -Charlie _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
