>Hi guys,
>
>How do you get around the performance issues. Using views has really slowed the data transfer at my location. I really like the idea about using remote views within the DBC (then I can use SDT to support simple changes) but I found major performance hits using views vs seeks. I mean big hits. It appears that views that use parms transfer the entire index just to get one record. I'm not totally sure of what I saying but it appears I'm right from past tests.
>John

Wow, Im not seeing this at all.

What size tables and params are you speaking of.

I can go on standard size of 30k + trans or killer of 1 million +. Neither are effected.

Passing the param is just waht you woudl do in true C/S anyway.

For my primary table that we use, the 30K one, is really a flat file. I know it hurts to say it, but it was necessary in this instance. There are too many percolations through normalized data that it can't be helped. But this makes it the WORST in views becasue it's got a length of 1105 characters.

There are 3 different params that are passed against this beast! Customer #, Shipping date, last_at.

Currently I'm working on Shippping so I get into that area.
CREATE SQL VIEW "LV_MASTER2_SHIPPING_all" ;
AS SELECT * FROM ves!master2 WHERE Master2.shipdate = { / / }

This also works as fast as a free table where ves!master2 is replaced with f:\pro30\custom\master2.

My form loads data with this type of call:
use LV_MASTER2_SHIPPING_all alias V_MASTER2_SHIPPING_all NODATA

I can now index the heck out of an empty shell. Requery() brings back the non shipped transactions that I need and the view has index tags already assigned that my grid will use.

The time it takes to bring all records to me is about 60 seconds. Remember that this is a huge file "WIDE" When I close all tables and then use my view above with data it takes just about 2 seconds tops to return 2600 + transactions. this is done after quitting VFP, starting word, quitting word, and then re-starting VFP, so it's not stored in memory.

I have another view that is an add to the V_MASTER2_SHIPPING_all. Add the param for custno and customer shipto. It takes less than a second to give me all unshipped items for this customer at that location.

So when you talk about performance I disagree. Views are teh way to go. Secondly I can upsize this mega table to SQLSERVER were it's performacne is really hurt by it's size, but it can still keep up on non shipped!.