yankel1
asked on
I can't open a Advantage Database view with sql
I made a view in advantage architect, I'm able to open it in architect just fine but when I type: SELECT *
FROM view1
I get an error.
what can I do?
my other views work as normal.
FROM view1
I get an error.
what can I do?
my other views work as normal.
AdsQuery1: Error 7200: AQE Error: State = 42000; NativeError = 2228; [iAnywhere Solutions][Advantage SQL Engine]Invalid view definition: View1. Unexpected token after the
view statement.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Let me repeat my point:
The error message in you original post indicates that there is a problem with something following the end of the SQL statement in the view. Normally, error messages such as this are generated because of extraneous (often non-displayable) characters following the desired SQL statement. They are not randomly generated.
Try highlightinh and copying the SQL in the View to a Notepad window, deleting the viewentirely, and then highlighting the text in the Notepad window and using it to create a new view.
Cycling the text of the SQL through Notepad will most commonly remove any extraneous trailing (non-displayable) characters.
also this view worked in the past!
So, what changed? Did you modify the view at some point (immediately prior to it starting to fail?).
The error message in you original post indicates that there is a problem with something following the end of the SQL statement in the view. Normally, error messages such as this are generated because of extraneous (often non-displayable) characters following the desired SQL statement. They are not randomly generated.
Try highlightinh and copying the SQL in the View to a Notepad window, deleting the viewentirely, and then highlighting the text in the Notepad window and using it to create a new view.
Cycling the text of the SQL through Notepad will most commonly remove any extraneous trailing (non-displayable) characters.
also this view worked in the past!
So, what changed? Did you modify the view at some point (immediately prior to it starting to fail?).
ASKER
also this view worked in the past!