I got error Nested Case When reached level t0 10. I got this problem while migrating my MSAccess Queries to MSSql server with SSMa migration Tool and another problem i have, Empty record is disabled in one of my form.Please help me.
I got error Nested Case When reached level t0 10. I got this problem while migrating my MSAccess Queries to MSSql server with SSMa migration Tool and another problem i have, Empty record is disabled in one of my form.Please help me.
I am sorry to say that this I found this request to be a bit confusing as it is currently worded. Most of the people who post in this particular Forum have worked with SSMA, so if you are able to provide a little more details, we might be able to assist. Showing the original SQL Code and the resulting SQL Code could be a great start.
I attached two Images. Image 1 represent the Access file as frontend and backend. Image :1
Image:2
Image2 represent Migrated Access file with access as front end and DB MSSQL server as backend using SSMA. That form having 3 fields. Mode_Milestone(Combobox), Percentage,NO of days.
In Image 1 file shows the combo box and Allow to enter data but Image 2 is not allowing to insert and all the fields are disabled.Another problem is one of subform is showing the same error.
I assumed that your problem was related to an IIf() statement based on your original post, and therefore was expecting to see SQL Code in Access Format, and SQL Code in SQL Server Format. The images provided do not show the information that i was looking for. Are you able to provide the SQL Code?
I assumed that your problem was related to an IIf() statement based on your orignal post, and therefore was expecting to see SQL Code in Access Format, and SQL Code in SQL Server Format. The images provided do not show the information that i was looking for. Are you able to provide the SQL Code?
Once in a while when I was using use the SQL Server Migration Assistant (SSMA) I discovered that the target SQL Server columns were not exactly the same as original Access ones. I then had to use the SQL Server Management Studio (SSMS) to verify that they were all the same, including Field sizes and data types, adjusting any that were not.