How large are your tables? I have similar situations where I have to open a view on a 50,000+ record SQL Server database as a remote view. It's none too swift, averaging about 15-30 seconds to come across a wide-bandwidth connection.

What may be a better solution is to create a preprocessed (right word?) view in your server database and open that. Let the server db do the work. Should be faster, in theory.


>I posted this in the client server section, but I failed to mention that I am using ODBC to talk to my database. That slows stuff down too. :-(
>
>I guess there is no easy answer. My current process takes about 30 seconds per master record.
>
>I wanted to avoid the slow startup costs of loading every record from every table at the start of the program, but I figured that I would have to deal with each master record only taking under 10 seconds. Not a half a minute.
>
>I'll pay the overhead at the top of the program. Tell the users not to exit during the day... *sigh* another plan gone astray.
>
>>>I have a parametertized view with six fields and one where condition, and nothing else. It takes about .5 seconds to requery() it. Is that normal?
>>
>>I've just been timing my code, and I have a fairly simple local view of 12 fields, 2 parameters in Where, and it takes about .012 seconds each requery from a fairly small table, small result set, with indexes on Where fields, not much longer without indexes. So there's very little overhead in a Requery() command itself. Slowness may result from lack of index on Where field, large result set, network overhead, perhaps, in your case...also, index on deleted can slow it down.