I have a vertical market application I've been developing for a year and half and am in the final rollout phase of the software. The February 29th and subsequent builds of V11 changed something in the Active Link tables connectivity so that all tables that I have built based on custom SQL statements that include a WHERE clause now fail when opened.
I have several tables that are connected as Active Link and I use the WHERE clause in the Active Link definition in order to maximize speed and efficiency of the application and limit the amount of data moved across the network. If I lose this functionality then the application becomes unusable (not to mention it would require rewriting major sections that already assumed the data had been filtered to include only the relevant information in the active link table!) As an example I have a table currentyear with the primary key being taxyear. When I use the custom SQL statement "Select * from currentyear" everything is fine but if I make that same statement "Select * from currentyear where taxyear = '2012'" I get the following message:
alpha_error.JPG
This error does not occur with builds 2373 or earlier.
I have submitted this bug to Alpha but this presents me with an uneasy feeling about the future of using Alpha for my company's products if new versions of Alpha can effectively make previously working programs I've created suddenly become unusable. That's why I test everything and I'm at least glad that Alpha makes previous builds available.
I'm hoping this was simply a bug introduced with changes and that Alpha will respond quickly to remedy this situation. In the meantime I've reverted back to the January 20th build and everything is working fine again.
I have several tables that are connected as Active Link and I use the WHERE clause in the Active Link definition in order to maximize speed and efficiency of the application and limit the amount of data moved across the network. If I lose this functionality then the application becomes unusable (not to mention it would require rewriting major sections that already assumed the data had been filtered to include only the relevant information in the active link table!) As an example I have a table currentyear with the primary key being taxyear. When I use the custom SQL statement "Select * from currentyear" everything is fine but if I make that same statement "Select * from currentyear where taxyear = '2012'" I get the following message:
alpha_error.JPG
This error does not occur with builds 2373 or earlier.
I have submitted this bug to Alpha but this presents me with an uneasy feeling about the future of using Alpha for my company's products if new versions of Alpha can effectively make previously working programs I've created suddenly become unusable. That's why I test everything and I'm at least glad that Alpha makes previous builds available.
I'm hoping this was simply a bug introduced with changes and that Alpha will respond quickly to remedy this situation. In the meantime I've reverted back to the January 20th build and everything is working fine again.