Hi.
My application is made with MSaccess2010.
It has multiple users, a split front end, and all users (and db) is on a citrix terminal server. This works great (enough). Backend accdb, frontend accde.
However, I see the need to upgrade the backend to SQL server and keep the frontend in access. The numbers of users increase, and so does the amount of data.
I have read about MsAccess 2013, and that 2013 has swapped the JET engine with Sql engine. Doesnt access2013 require a server for its SQL engine, is it a desktop sql server within the application...?
Can I just "convert" my 2010 backend to an Access 2013 DB, and "automatically" get a SQL engine? This sounds to easy...And if this is correct, can I keep my 2010 frontend as is, and use msaccess 2010 application for the frontend to mye users?
I want a SQL backend for better safety. I have had one incident of data corruption, and thats one to many.
Hope for an answer!
My application is made with MSaccess2010.
It has multiple users, a split front end, and all users (and db) is on a citrix terminal server. This works great (enough). Backend accdb, frontend accde.
However, I see the need to upgrade the backend to SQL server and keep the frontend in access. The numbers of users increase, and so does the amount of data.
I have read about MsAccess 2013, and that 2013 has swapped the JET engine with Sql engine. Doesnt access2013 require a server for its SQL engine, is it a desktop sql server within the application...?
Can I just "convert" my 2010 backend to an Access 2013 DB, and "automatically" get a SQL engine? This sounds to easy...And if this is correct, can I keep my 2010 frontend as is, and use msaccess 2010 application for the frontend to mye users?
I want a SQL backend for better safety. I have had one incident of data corruption, and thats one to many.
Hope for an answer!