.ADP file conversion to .ACCDB format - Access 2013
Hi,
As we all know that access ADP format have been deprecated from Access 2013.
I am required to migrate ADP format to ACCDB Access 2013 format. we have been able to import all the forms in the new file, however we got stuck in stored procedures as they are not supported by Accdb format. These procedures are being used in forms to pull data from SQL Server. We are using SQL Server 2012.
It would be great if anybody can suggest the solution.
Regards,
Rahul
As we all know that access ADP format have been deprecated from Access 2013.
I am required to migrate ADP format to ACCDB Access 2013 format. we have been able to import all the forms in the new file, however we got stuck in stored procedures as they are not supported by Accdb format. These procedures are being used in forms to pull data from SQL Server. We are using SQL Server 2012.
It would be great if anybody can suggest the solution.
Regards,
Rahul
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
PatHartman
For single record (or small quantity) recordsets, stored procedures offer no advantages over standard bound forms. I would cut the cord entirely rather than worrying about side effects.
Hi Pat,
that depends on what the SP does. If it is only a replacement for a view with parameters then you're right, a simple linked view with parameters in the frontend is enough in that case. But often SPs are created to do complicated calculations, summations, procedural code and so on - there's nothing which could replace that in the frontend which would make sense because that's the real power of using a database server: Having an active backend which can do all the heavy data work and only return the result.
Cheers,
Christian
that depends on what the SP does. If it is only a replacement for a view with parameters then you're right, a simple linked view with parameters in the frontend is enough in that case. But often SPs are created to do complicated calculations, summations, procedural code and so on - there's nothing which could replace that in the frontend which would make sense because that's the real power of using a database server: Having an active backend which can do all the heavy data work and only return the result.
Cheers,
Christian