Re: RADiest Client for SQL Server
From: Michael C (mculley_at_NOSPAMoptushome.com.au)
Date: 11/17/04
- Next message: BIN YANG: "Error 3140 on SQL Server 2000"
- Previous message: Mike Epprecht \(SQL MVP\): "Re: Need an elegant solution around SQL Server Limitations"
- In reply to: Mike MacSween: "Re: RADiest Client for SQL Server"
- Next in thread: Mike MacSween: "Re: RADiest Client for SQL Server"
- Reply: Mike MacSween: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 10:24:28 +1100
"Mike MacSween" <mike.macsween.nospamplease@btinternet.com> wrote in message
news:419bcb62$0$216$5a6aecb4@news.aaisp.net.uk...
> What is it about the words 'One day somebody might' and 'but for now' that
> you find difficult to understand?
These are very grey terms, the fact the you specified it means that it is a
consideration of the project. I usually plan for the future.
> As for web pages being as good a client as Access front ends, just give me
> the URL of one. And no, to be honest I've no interest atall in spending
> 100s of hours wrestling with another new technology in order to give
> somebody a web interface into a database that lives on the same machine.
What is it about the words 'If that's the case then I wouldn't recommend a
web page.' that you find difficult to understand? :-)
> So, you clearly have great experience of Access and know it's limitations
> very well. In which case, given that it's the only thing I know well, and
> that there isn't time or inclination to learn anything else, and it will
> at least _work_, which is the lesser of the the two Access evils? ADP or
> MDB? You see to know a lot about it, so I am sure you will have good
> advice.
I've mainly used access as the backend and only as front end in very small
projects. I believe ADP is designed specifically for SQLServer so why not
use that?
>> It might be slower than access.
>
> Oh good, that's a real recommendation.
The fastest way to do something is rarely the best.
> how better?
In too many ways to list. :-)
Michael
- Next message: BIN YANG: "Error 3140 on SQL Server 2000"
- Previous message: Mike Epprecht \(SQL MVP\): "Re: Need an elegant solution around SQL Server Limitations"
- In reply to: Mike MacSween: "Re: RADiest Client for SQL Server"
- Next in thread: Mike MacSween: "Re: RADiest Client for SQL Server"
- Reply: Mike MacSween: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|