Hello,
We want to migrate the data tables only to SQL SE but keep front end the same, which I understand is not a overly complicated thing to do in itself. However, to make it efficient and not run into a lot of network-caused slowness, I understand that the queries that are needed for reports and for producing read-only datasets have to be re-written as pass-through in the SQL that SQL Server understands. Fine, we can make that happen (I would get help from someone who can do this re-writing).
But what will happen to the bound forms which the users are using to edit data in the tables? All those forms are bound to editable query sets and that's how the users interact with the tables. Could the queries behind those forms stay the same- meaning in Jet sql? And if they do stay the same, will they be really, really slow and would the userhave to sit there forever and ever for each edit they make to a record to be saved?
Also, I have a number vba procedures in this database that use sql statements created directly in the code. Those statements are used by two kinds of vba procedures:
-snippets of code in forms' on load events that set the row source of some of the forms' controls
-larger code procedures that take datasets from stored queries as well as sql strings defined directly in the vba code and paste it into excel reports.
Would it be possible and advisable to leave the sql strings in vba as they are- written in Jet SQL? Or does everything have to be re-written for SQL Server?
Both parts of this question are important points for me, but if you have any advice on either one of them, I would be very grateful.
Thank you.
We want to migrate the data tables only to SQL SE but keep front end the same, which I understand is not a overly complicated thing to do in itself. However, to make it efficient and not run into a lot of network-caused slowness, I understand that the queries that are needed for reports and for producing read-only datasets have to be re-written as pass-through in the SQL that SQL Server understands. Fine, we can make that happen (I would get help from someone who can do this re-writing).
But what will happen to the bound forms which the users are using to edit data in the tables? All those forms are bound to editable query sets and that's how the users interact with the tables. Could the queries behind those forms stay the same- meaning in Jet sql? And if they do stay the same, will they be really, really slow and would the userhave to sit there forever and ever for each edit they make to a record to be saved?
Also, I have a number vba procedures in this database that use sql statements created directly in the code. Those statements are used by two kinds of vba procedures:
-snippets of code in forms' on load events that set the row source of some of the forms' controls
-larger code procedures that take datasets from stored queries as well as sql strings defined directly in the vba code and paste it into excel reports.
Would it be possible and advisable to leave the sql strings in vba as they are- written in Jet SQL? Or does everything have to be re-written for SQL Server?
Both parts of this question are important points for me, but if you have any advice on either one of them, I would be very grateful.
Thank you.