On Apr 30, 2:55 am, teddysn...@hotmail.com wrote:
> Having upsized my client's back-end DB to SQL Server, the following
> query does not work ("Operation must use an updateable query").
[quoted text clipped - 39 lines]
>
> Edward
what's the problem with using a passthrough query ?
teddysnips@hotmail.com - 30 Apr 2008 11:49 GMT
> On Apr 30, 2:55 am, teddysn...@hotmail.com wrote:
[...]
> what's the problem with using a passthrough query ?- Hide quoted text -
The database was developed by a gifted amateur, who more or less
taught herself Access as she went along. I've been asked to do the
upsizing to SQL Server, but I want to keep any modifications to the
front end as simple and close to standard Access as possible.
Edward
Roger - 01 May 2008 02:40 GMT
On Apr 30, 4:49 am, teddysn...@hotmail.com wrote:
> > On Apr 30, 2:55 am, teddysn...@hotmail.com wrote:
> [...]
[quoted text clipped - 6 lines]
>
> Edward
ok, using access97, I created 2 tables with two fields each (removing
spaces in field names) and this query runs with no problem
tblBookings
transFromId bookingId
1 2
tblRefunds
bookingId movedToNewBkref
1 0
UPDATE tblbookings INNER JOIN tblREFUNDS ON tblbookings.TransFromID =
tblREFUNDS.BookingID SET tblREFUNDS.MOVEDTONEWBKREF = tblbookings!
bookingid
WHERE (((tblREFUNDS.MOVEDTONEWBKREF)=0) AND
((tblbookings.TransFromID) Is Not Null));
after running the query, movedToNewBkref = 2
so I'm not sure why you're getting this error
Larry Linson - 01 May 2008 00:29 GMT
> what's the problem with using a passthrough query ?
The usual problem with a passthrough query is that Access/Jet-ACE has its
own dialect of SQL, and the back-end servers all have their own dialects of
SQL. Unless the users go 'way out of their way to adhere to ANSI-standard
or world-wide-standard SQL (and, it is amazing how many, even when their
projects claim "industry-standard", do not) those will not be the same.
Some developers or SQL-addicted-hobbyists may revel in knowing second-nature
all the major / minor / obvious / subtle differences, but typical users
(and, I suspect, typical developers) generally limit their scope to one
"dialect".
Jet and ODBC, in my experience, translate Jet SQL to surprisingly "good",
efficient server SQL when the user creates the Query in Access. It's not as
good as a 'rockstar' DBA or server Developer could do in a world-class
competition, but better than one might expect.
Larry Linson
Microsoft Office Access MVP
On Apr 30, 3:55 am, teddysn...@hotmail.com wrote:
> Having upsized my client's back-end DB to SQL Server, the following
> query does not work ("Operation must use an updateable query").
[quoted text clipped - 39 lines]
>
> Edward
I think the query you wrote in QA will work in Access if you get rid
of the table aliases 'r' and 'b' or create the aliases using
'as' (e.g. 'tblBookings as b' and 'tblRefunds as r'). The Access
syntax is a little bit different than the TSQL syntax but I don't
recall the exact differences.
Did you recreate your unique indexes on the SQL side? Both tables
being joined must have unique indexes. I do not trust the upsizing
wizards to get this right, if that's what you used to move your data
to SQL server.
Bruce