>
>QUESTION:
>What could be a reason to use three-tier architecture with an OLE Server rather then calling SQL Server stored procedures?

Speed for one thing. It is also possible that business rule could be difficult to represent in a stored procedure.

>
>I know one is that i can write business-rules in my familair language VFP but i wouldn't realy care to learn SQL Server language.
>

Why? You'll be learning skills that will help you in the future.

>I have been thinking about a possible pro of using multi-tier architecture but i am not sure this is true: Can i develope OLE objects like navigation buttons where for instance the skip button is disabled when the end of the file is reached and use this object in Visual FoxPro Access and Visual Basic?
>

In a C/S design, you don't get all the records. You send a query to the back end for a set of records. For example "Show me all the customers that live in Utah". The previous, next, etc will then work on that set of data rather than the entire database.

>I realy need to know the pros and cons in order to make the right decission.
>Thanks for any reply,
>
>Marco.