Re: RADiest Client for SQL Server
From: rkc (rkc_at_yabba.dabba.do.rochester.rr.bomb)
Date: 11/17/04
- Next message: Kevin Lorimer: "RE: Previous Working Days"
- Previous message: Kraft, Norbert: "Re: setting Startup service account of a machine via SQL-DMO"
- In reply to: Mike MacSween: "RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 17 Nov 2004 12:05:12 GMT
"Mike MacSween" <mike.macsween.zerospamplease@btinternet.com> wrote in
message news:419a6b0c$0$218$5a6aecb4@news.aaisp.net.uk...
> I've got a SQL Server database. Nearly finished. It's going to go on a
> single non networked machine. One day somebody might get access to it over
> ADSL (probably TS), but for now it's a single user no lan.
>
> The machine will actually be running the MSDE. Windows XP Home.
>
> I'm quite happy, for now, to put all the business logic in SQL Server.
> Triggers, SPs etc.
>
> I've got a fair bit of Access development experience.
>
> What's the absolute quickest way to develop a client for this?
>
> MDB or ADP client?
> OLE-DB or ODBC connection?
> Bound or unbound
>
> My experience is with Access 97/2000 FE/BE type apps.
The fastest way, without learning anything new at all, is to link to
the msde tables and ignore all the benefits of using msde. Simply
treat it as if it were a Jet. database in another .mdb file.
- Next message: Kevin Lorimer: "RE: Previous Working Days"
- Previous message: Kraft, Norbert: "Re: setting Startup service account of a machine via SQL-DMO"
- In reply to: Mike MacSween: "RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
