Hi Jerry;

You will need to make sure that your remote view is parameterized so that you do not select all data when you open the view. If you do not add a parameter (such as keyfield = "xxx") opening the view is the same as doing a SELECT * which will try to download ALL 1.5GB. This is probably not what you want to do!

In the view designer, create a parameter (or parameters) equal to the primary key or other fields in the database. In the Filter tab create a condition such as = ?viewparm.

For instance if you have a table called cities and a field called city your filter clause would be
cities.city = ?v_city

If you have pre-initialized v_city the view will open without any prompts. If not, you will be asked to enter the city.

This works very well, but implies that if you have multiple conditions (sometimes city AND street, etc) you may need multiple views.

Bob


>I have a 3.5G database containing a table that is 1.5G that will grow quite large. I wish to run some queries off of it in VFP 5 and just return the results.
>
>Although I've programmed in Fox since '84, I'm not very familiar with SQL Server (6.5).
>
>When I try to use a remote view that I created, I get an ODBC error that says my temdb is full (I increased it to 7 MG). If I am not filtering in my remote view, I think I would need to have a tempdb of the equivalent size of the largest table in my database. Is this a correct assumption?
>
>Is there a way around this?
>
>Eventually I will be linking up FoxFire! to this and coding it such. But I would like to just send the query across and receive only the selected records. If I use VFP's GUI SQL creator, I need to load a table or view. If I load the view (containing all the records), I need a HUGE tempdb....help!
>
>there's gotta be an easy way out of this....
>
>