"Matthew Jones" wrote:
<<
Yes, I agree, but this is a big change, so why not benefit from it?
>>

Depends on your tolerance for risk - OP mentioned that he is not writing a new app, just switching  the distribution to SAAS model. Hence the question  - do you want to introduce 2 possibly major changes simultaneously ?

<< Having done that, switching to EDB was simple, as the changes were
encapsulated in one place. The component is nothing fancy - plenty of
schemes people made that do very clever things but they aren't my
style. But this has made my SQL so much clearer and simpler. (Not
trying to convert anyone here, just saying that if you've had a desire
to do something like this, make it happen as I wish I'd done it years
ago!)
>>

This is a good idea and something that might be worthwhile. The challenge again is changing existing code - nice thing is that one could add this into DBISAM code preparing for future.


At the end of the day for us this comes down to cost/benefit  of change and technical debt - I can assure you we have analyzed the heck out of it and today the benefits for us are not there yet for upgrading an existing app. Doing a new app would be a different story.

Raul

Colin,

<< Hi, I'm changing the way I am distributing my software from a model where the application resided on the client's server, to a SAAS style where I will now host my software on our own servers.  I'm specifically wondering how memory tables will work in the new environment. >>

I assume that you're using terminal services or something similar ?  If so, then you won't need to change anything in your application.  It will keep on working exactly the same as it always has.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


He's using TSPLUS

Roy Lambert