Upgrade to 5991-5333 introduced errors in SQL / Lists

[PhotoHog]

Hi all

Just upgraded to 5991-5333 from 5887_5315 - well that was short lived - had to revert back to 5991-5333.

It looks like Alpha has changed how the SQL is built in a list control and I was getting 2019-07-30_1517.png.

This caused me to get a script error when trying to preview the component.

I read the release notes - I did notice that Windows XP is no longer supported. I have a desktop that runs XP and a laptop that runs W10. I tried on both with the same result.

Anyone else experience anything like this?

Thanks

Darren

[iRadiate]

Re: Upgrade to 5991-5333 introduced errors in SQL / Lists

I am not experiencing that issue with SQL derived lists.

[PhotoHog]

Re: Upgrade to 5991-5333 introduced errors in SQL / Lists

UPDATE: I have been doing some testing and I think I have found the issue - I need some advice on how to deal with it.

I am working with data that came from MS Access Database that was implemented in the early 1990's. The original designer used a lot of field names with spaces, which Access allowed. For example "Last Name" as a field name. When I link to these tables the SQL builder in Alpha would write the SQL as: SELECT Customers.[Last Name] AS Last_Name and this worked fine. When I updated I started getting the EOF expected as - see the graphic in my original post.

If I go back to my tables and fix the field names so that there are no spaces, the error disappears. The problem is we still use MS Access to do some work on the tables and changing the field names at the source would cause me huge issues on the MS Access end.

I could build a view for each table and then revamp all my lists to attach to the views not the tables, but that would be a HUGE amount of work and involve a lot of work

Or is this a bug that Alpha should fix?

[Selwyn Rabins]

Re: Upgrade to 5991-5333 introduced errors in SQL / Lists

Hi all

Just upgraded to 5991-5333 from 5887_5315 - well that was short lived - had to revert back to 5991-5333.

It looks like Alpha has changed how the SQL is built in a list control and I was getting [ATTACH=CONFIG]46075[/ATTACH].

This caused me to get a script error when trying to preview the component.

I read the release notes - I did notice that Windows XP is no longer supported. I have a desktop that runs XP and a laptop that runs W10. I tried on both with the same result.

Anyone else experience anything like this?

Thanks

Darren

There was a change made to the sql builder (noted in the release notes) to format the sql in a more readable way. each field is shown on its own line.

it looks like that change is affecting you. we would need to get a copy of the sql statement to see why the sql parser does not correctly parse it now.

[PhotoHog]

Re: Upgrade to 5991-5333 introduced errors in SQL / Lists

Here's an example from a test that I built


SELECT Leads.LeadID, Leads.LeadApptDate, Customers.[Last Name] AS Last_Name, Customers.[First Name] AS First_Name, Customers.Street
FROM Leads Leads
INNER JOIN Customers Customers
ON Leads.CUID = Customers.CUID

[Selwyn Rabins]

Re: Upgrade to 5991-5333 introduced errors in SQL / Lists

Here's an example from a test that I built


SELECT Leads.LeadID, Leads.LeadApptDate, Customers.[Last Name] AS Last_Name, Customers.[First Name] AS First_Name, Customers.Street
FROM Leads Leads
INNER JOIN Customers Customers
ON Leads.CUID = Customers.CUID

this has been fixed. ifyou go to the release notes for build 6012 you will see a hotfix for this issue