>>Experience with what? With SEEK or with SELECT_SQL?
>>Sorry, but your answer smells bad.
>>
>>>Looks like you have no experience with this Ed. When you do, then we'll talk.
>>>
>>>
>>>>Well, some points are too obvious to be discussed even, but why do you put SEEK to 'prohibited' list? Do you want to look for one/few record(s) in 10 millions using SELECT-SQL? It's about the same as using rockets for sparrow hunting.
>
>Ed
>
>Given a SQL Server or Oracle backend, how else would you propose finding a single row out of millions... Even if designing a system using native tables, to ensure an upgrade path using a SEEK against base tables strikes me as a bad idea.

Mark,
The post was not specifically about RDBMS back-end. This is obvious that many people around including myself are intelligent enough to know that SEEK() can be used for native VFP engine only and cannot be used for RDBMS. Sorry, that I have to tell you these facts now.
The problem (if we are still on technical groud) is that a developer cannot design his/her system blinfolded. It means that the first responsibility to assess scope of project, and if situation assumes that VFP interface will use native data, then this developer must use the most efficient way to develop this system. If someone does know what is SEEK about, then 'future upgrade' to RDBMS is really lame excuse.