> Scot, > Yep, Gigabytes. > > And soon to be larger. > That's why I migrated it to SQL Server :-) They say SQL server is only limited in size by the time it takes you to back the thing up..... > I understand that the tempdb is used for all queries and is not dynamic > (too bad) - and Yes, I will need the capability of storing my entire > largest table in the tempdb (unfortunately) - here's why: I would try to increment the size peice by peice untill you can do the query then. Try adding devices, say 50 Meg at a time, and use the "expand' feature (From Enterprise Manager, right click on TempDB and choose edit, then expand it from there). I would think you are hitting the point where the server is pushing the data into TempDB faster then ODBC can shove it out. I would doubt that you would need to expand it by 1.6 Gigs, however. (If you do, call M$ and complain (s)) > The users will be running queries to their heart's content. I can not > control or limit these - at least I haven't figured out a user friendly > way to do this ("Joe" wants all history from the past 3 years. Doesn't > really know what he's looking for - If I limit the query, I would have to Well, then "Joe" will have to explain to your boss why you need a 2 gig drive just so you can make your TempDB big enough, than wouldn't he? (LOL) you can be mean and li,it the number of rows (g). It's not all that uncommon in the industry. I tell my users here to inform me if they expect to have a result larger than 10,000 rows. I don't need one user bogging down the whole system because he/she is "just browsing" (pun intended (s)). > read his mind and although I HAVE been getting better at that...<g> It's a skill you will never quite master but one you cannot live without....(g) > I just wish tempDB was dynamic - If the user ran a HUGE query, swap the > information - slow down the query - at this point they deserve it. I wonder.....how many rows are you fetching at a time in VFP5? Perhaps you can play with that setting to paramterize your view not based on a where clause, but rather on the number of rows. Check that setting in your view properties. Good luck, and keep me informed (I am curious as to how this works). HTH, Scot.