|
|
Posted by David Portas on 09/26/68 11:44
javelin wrote:
> I know, that statement can make me lots of enemies. I am sorry, but
> I've worked with a SQL Server back end with an MS Access ADP on the
> front end, and the process of creating queries, and especially update,
> insert and delete queries is SO much easier in Access.
Is it a query "designer" you are looking for? I don't know anyone who
uses those things. Take the trouble to learn to write your own SQL.
You'll write much better, faster code and you'll *understand* what you
are doing instead of wasting time drawing pretty diagrams and filling
in grids :-). Quite honestly, Query Analyzer or SQL Server Management
Studio is the best place to do any serious work.
> I didn't think
> I'd miss it when I moved over to an environment managing about 160
> "nearly identical" databases across several servers. I was wrong.
That doesn't sound like a great architecture to me. What's the
rationale for having 160 near identical databases?
> I suppose I can create a front end file for each of the back end
> databases, but it's not practical timewise to create them all. I wonder
> if it's possible to create one and run some VBA code to change the
> connection string.
That's an Access question. Certainly it is possible in .NET. All the
noises coming out of Microsoft now seem to stack up against using ADP
however. I don't keep in close touch with Access product developments
and things can always change but at the moment it seems like MS expect
you to move away from that technology.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|