Hi

I have an app running in C/S mode. But I would like to deal with memory tables completely at client side. IOW, The session + database + table will be local. Should I have a local engine too ? I understand I need to set configuration "in memory" and at the beginning of app the session + database should be created and the "memory" database created too for use with local memory tables.

Thanks for any tip. BTW I am trying to figure out until any comments.

Eduardo

Jose


>I have an app running in C/S mode. But I would like to deal with memory tables completely at client side. IOW, The session + database + table will be local. Should I have a local engine too ? I understand I need to set configuration "in memory" and at the beginning of app the session + database should be created and the "memory" database created too for use with local memory tables.

I can recall these sort of questions before and I think the answer is still the same. Essentially you do have it right. There is one really important thing to remember if you use a separate session for a local in-memory database. You will not be able to use SQL between the local and remote session.

If you leave the in-memory database with the c/s remote session you also need to realise that unlike DBISAM a table created in the in-memory database is shared between users. If you want private tables you have to create them as temporary tables. One consequence of this is that if you have several users all creating in-memory tables in the same in-memory database you can get name clashes unless you use temporary.

Roy