I have to say though I do find it takes longer and the tools arent nearly as good (even in the newer versions e.g. sql 2005) to craft stored procedures...

Im with the stored procedure side as well - especially as my systems grow into several different front end technologies, I like to centralise the business logic so its written...

I had a similar problem with a query that was being run in a ms access front end vs. me trying it directly on sql server. Access was taking 30...

I applied the sp2a (as instructed), it gets 1/2 way through updating the database engine files and hotfix.exe crashes. Lovely

Going through the documented...

"I see that the number of bad managers has been increasing in recent years. Is this my imagination or has there been a change for the worse?"

In my experience, its...

a developer friend of mine works for a very large company

they spent a long time and much money converting all of their systems and data handling to use xml instead...

you could also keep using access, but start moving over functionality and application logic directly onto SQL server itself.

That way you can lock the data down at source, rather than...

i normally do it using faster direct sql access, but sometimes the ms access way is quicker and easier to get a job done in very short space of time...

good man

i think macros should be banned.

*shivers in horror at some of the access systems hes had to debug someone else has written...

cant you just not use macros?

use code instead?

martin

sounds to me like your access is independant of the problem, the calling a SP from inside another SP is purly sql server, so don't worry about the access bit.

If...

I was going to say as well, shouldnt it be </features> at the end? So what would the result be with that error! I thought it would be `0` due...

can you give them access to the data via a view instead of the table directly?

you might be able to do something with that!

martin

there has recently been another thread on fixing problems with access databases, you might liek to check that out

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=131&messageid=227550&p=1

martin

you can also physically limit them from typing in more than a specific number of characters on the fly

you need to stick a line of code on each control you...