Re: RADiest Client for SQL Server
From: Mike MacSween (mike.macsween.nospamplease_at_btinternet.com)
Date: 11/18/04
- Next message: Danny: "Re: SQL statement for report..."
- Previous message: David Portas: "Re: Access .adp :How to INSERT all but KEY violations"
- In reply to: Michael C: "Re: RADiest Client for SQL Server"
- Next in thread: Michael C: "Re: RADiest Client for SQL Server"
- Reply: Michael C: "Re: RADiest Client for SQL Server"
- Reply: Norman Yuan: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 00:06:58 -0000
"Michael C" <mculley@NOSPAMoptushome.com.au> wrote in message
news:uGi2KvPzEHA.1392@TK2MSFTNGP14.phx.gbl...
> 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?
So were they MDB front ends or ADP front ends? I know about Access as a back
end
>> how better?
>
> In too many ways to list. :-)
Well make a damn start!! Don't make smart alec comments about how such and
such a thing is better if you're just going to keep it to yourself. If .net
is so massively better than Access as a client to SQL Server then just tell
us the first 10. At least I could look at them and see if it's worth loading
my copy of VS.net onto the machine.
Mike
- Next message: Danny: "Re: SQL statement for report..."
- Previous message: David Portas: "Re: Access .adp :How to INSERT all but KEY violations"
- In reply to: Michael C: "Re: RADiest Client for SQL Server"
- Next in thread: Michael C: "Re: RADiest Client for SQL Server"
- Reply: Michael C: "Re: RADiest Client for SQL Server"
- Reply: Norman Yuan: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
