Problems with SQL Server on Azure VM

Scriptcase 9
#1

Hi
Am looking to port an existing Mysql Scriptcase suite (around 200 apps) to Azure.

Azure SQL is SQL Server.

I have created a copy of the database in Azure… But Azure appears to prefix the schema to the table name.

I can connect fine to the database and as long as there are no ‘select’ or other lookup fields everything works fine.

HOWEVER, when I have a form with a lookup, it will not compile and throws an error:
image

This is with a brand new grid/form, just generated from the Azure table.

In addition, my suite has many/many lookups and I simply cannot go back and recreate them with a table/schema prefix.

Excuse my limited SQL Server experience, but is there any way of avoiding these problems?

if not then a port is simply not practical!

#2

in your where you did not mark your field with quotes,
so in your WHERE project_ref = ‘{project}’
and not WHERE project_ref = {project}

#3

Except the entire lookup was done by scriptcase. I didn’t manually edit it at all! I presume because it is an external constraint in the database.

Plus the first fail lookup has no field names.

#4

we can see in the request that the from table is a variable punctuated by a single quote, there is an error in this search, I would advise you to contact the scriptcase hepdesk by opening a ticket, they will be able to answer you more precisely

#5

Yes, I think this should be double quoted.

I fixed it manually and it worked.

A bit worrying that I had to intervene manually. I’ll update when I dig a bit deeper.

#6

Just a quick update…
The problem was a little intermittent, but I got it working… just not sure how! :blush:

I also ported to an Azure MySQL database, which also worked fine.

A fully tested port would take some time (hardening security, etc), but basic port testing was only a day or so and I had my suite of apps working properly under Azure.