Re: Upsize to SQL Server
- From: Bernard Peek <bap@xxxxxxxxxx>
- Date: Mon, 14 Nov 2005 13:57:43 +0000
In message <1131968189.797295.285650@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, lylefair <lylefairfield@xxxxxxx> writes
IMO there is no good way to use MS-Access with MS-SQL Server. A satisfactory way might be to use a disconnected ADP (a disconnected MDB is unlikely to be a lot different) and unbound Forms and Reports, or Forms and Reports bound to ADO recordsets (often disconnected). But this method does not fit with the RAD notion of Access. I've not worked with MDB-ODBC-MS-SQL Server. Perhaps, I should. I feel that with such a model, it will not be easy for me to use the power of T-SQL; I feel uneasy about interjecting an additional connection layer between the app and the db; I feel uneasy about the many posts here about problems associated with this model.
Access is a very popular program, lots of people use it therefore lots of people can be expected to have problems with it.
Personally, I have used MDB-ODBC-SQL for a lot of small projects and I haven't had any real problems with it. It's quite easy to develop an application using local Access tables then switch it to attached SQL tables. I use T-SQL when it gives me some positive advantage over Access, enough of an advantage to justify the extra work. I can either use T-SQL on the server to create a view or I can write a pass-through query in Access and send raw SQL up to the server.
-- Bernard Peek London, UK. DBA, Manager, Trainer & Author.
.
- References:
- Upsize to SQL Server
- From: dreadnought8
- Re: Upsize to SQL Server
- From: lylefair
- Upsize to SQL Server
- Prev by Date: Re: Private versus public variables and error handling
- Next by Date: Records getting lost
- Previous by thread: Re: Upsize to SQL Server
- Next by thread: Re: Upsize to SQL Server
- Index(es):
Relevant Pages
|