Re: Converting Application from ADP to ACCDB
- From: Tom van Stiphout <tom7744.no.spam@xxxxxxx>
- Date: Tue, 09 Jun 2009 20:38:18 -0700
On Tue, 9 Jun 2009 09:49:01 -0700, PGallez
<PGallez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
SELECT stored procedures are NEVER updatable. If you have middle-ware
smart enough to derive the corresponding UPDATE or INSERT statement,
great, but I don't think Access the way you describe it is one of
them.
What is wrong with linked tables/views?
What is unsafe about ADP?
-Tom.
Microsoft Access MVP
Although I'd rather stick with the ADP format when writing applications that.
use Access as a front-end to SQL Server, just to be safe I'm trying to work
out how to talk to SQL Server from an Access 2007 ACCDB file. My question is,
can all of the following requirements be met simultaneously (especially using
bound forms and an updateable recordset)?
1) Access ACCDB talking to SQL Server 2005.
2) Either ADO or DAO, but preferably ADO.
3) Bound forms (but NOT directly to a linked table or view, instead to an
ADO or DAO recordset based on parameterized stored procedures).
4) The recordset is updateable.
I can do all of the above using pass-through queries, except a PTQ isn't
updateable. I'd rather not move to an unbound form model because of the
substantial increase in coding required. Likewise for doing the development
in Visual Studio.
Any suggestions re whether this can be done, and if so, how?
- Follow-Ups:
- Re: Converting Application from ADP to ACCDB
- From: PGallez
- Re: Converting Application from ADP to ACCDB
- References:
- Converting Application from ADP to ACCDB
- From: PGallez
- Converting Application from ADP to ACCDB
- Prev by Date: Re: MS Access project cant find query
- Next by Date: Re: MS Access project cant find query
- Previous by thread: Converting Application from ADP to ACCDB
- Next by thread: Re: Converting Application from ADP to ACCDB
- Index(es):
Relevant Pages
|
