Re: RADiest Client for SQL Server
From: Michael C (mculley_at_NOSPAMoptushome.com.au)
Date: 11/17/04
- Next message: DWalker: "Re: Update time"
- Previous message: raydan: "Re: Divide By Zero Error in VIEW SQL"
- 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 08:33:41 +1100
"Mike MacSween" <mike.macsween.zerospamplease@btinternet.com> wrote in
message news:419af009$0$214$5a6aecb4@news.aaisp.net.uk...
> OK, once again. The database and the client software to access it will be
> located on a computer. One computer, located at the customers office. The
> customer will look at a monitor that is connected to this computer, via a
> 2 metre VGA cable.
OK, I was taking into account this statement as being more solid than it
obviously was. If that's the case then I wouldn't recommend a web page.
"One day somebody might get access to it over
ADSL (probably TS), but for now it's a single user no lan."
> I disagree completely. I've yet to see a web page that allows keyboard
> shortcuts.
For the keyboard shortcuts you are right.
> Or form/subform relationships.
I don't see the problem, it just depends how you write the web page.
> Or the ability to format reports based upon the data values in the
> datasource.
For the reports I use activereports which gives me *far* more control than
access and I can show the same report in a web or windows app.
> Or bound forms.
That's a programming feature.
> With the form level events that I can use to run code.
Another programming feature but asp.net does have this.
> I haven't got a clue what you're talking about. My question was perfectly
> clear.
Maybe you did it subconciously then? It's common for programmers to word the
requirements for the project to fit their favourite tool, which I find is
especially common for access programmers.
> So you mean MDBs or ADPs. Bound or unbound forms? OLE-DB or ODBC
> connection?
Write the damn thing in dot net and be done with it. :-) It might be slower
than access but you'll get a better end product and you can develop tools
for your next project. :-)
Michael
- Next message: DWalker: "Re: Update time"
- Previous message: raydan: "Re: Divide By Zero Error in VIEW SQL"
- 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
|
