Hi Rick! The only thing that I want to know is about how people takes care of table buffering issue. Personally, I use the technique that is similar to Edward Pikman's, but I think that there is another (may be better) way to do this stuff... that's why I'm read carefully all messages in this thread... One question: is the OLE server too powerful for just a desktop application? I think that any thin client should be very fat in this case to handle OLE server too ;))) Well, let we assume that we have network with thin clients and one fat that should handle OLE server. In this case the network traffic will be too heavy... I should agree with you that in WWW-development case the OLE is only way... Have a happy day Vladimir Shevchenko > >to RAD. Any thoughts and ideas are welcome ;) > I think you misread that. OLE Automation servers should only be > > * Classes that are in heavy use and might need to be remoted to > other machines. The move from Automation to DCOM is relatively > painless and requires no code changes on the client. > > * Web applications. This is really an extension of the first > point as you're interfacing VFP into other technologies. > ISAPI (Web Connection, FoxISAPI) can call Automation servers, > Active Server Pages can instantiate Automation objects directly > of ASP pages. > > > +++ Rick --- >