Jamie Collins said:
What did you have in mind here?
What I had in mind, was the warning in the page you linked to
yesterday;
"Why you should avoid mixing queries created under different ANSI SQL
query modes" at
http://office.microsoft.com/en-us/assistance/HP030704831033.aspx
Here using the example from the page, the stored query with the funny
aliasing.
Sub CreateTest()
Dim cn As ADODB.Connection
Set cn = CurrentProject.Connection
On Error Resume Next
cn.Execute "DROP TABLE Orders"
cn.Execute "DROP VIEW testOrders"
On Error GoTo 0
cn.Execute "CREATE TABLE Orders (" & _
"OrderID Int Identity PRIMARY KEY, " & _
"Freight Decimal NOT NULL DEFAULT 0)"
cn.Execute "INSERT INTO Orders (Freight) VALUES (100)"
cn.Execute "CREATE VIEW testOrders AS " & _
"SELECT Orders.OrderID AS Freight, Orders.Freight, " &
_
"[Freight]*1.1 AS [New Freight] FROM Orders"
End Sub
Doubleclick the query in the database window in both modes, and pretend
the query is the recordsource of a vital report.
