a said:
I'm just not sure I agree.
Using a numeric datatype-- would allow for better 'information
quality'.
It would be easier to test.
You're talking about checking to see if the field has all digits, right?
That doesn't seem very hard to test.
_EVERY_ single straw-- where SQL is better than Access-- is enough to
break the camels back.
A single straw-- for example 'optimal datatypes' is plenty reason to
move to SQL Server.
We're only talking about one straw and one that is not "plenty reason"
to move to SQL Server.
Access doesnt' support SmallDateTime, it doesn't even support varchar.
Everything is unicode with Access.
That's just another, different small straw.
SQL Server is faster, easier.
Probably not.
Sorry-- but just because you're stuck in the 80s; that doesn't mean
that Access is inherently 'easier' than SQL Server.
SQL Server makes sense.
Access is inherently easier than SQL Server. Plus, one might argue that
anyone who uses SQL at all is stuck in the 80's. Yet it would not be
practical to give up archaic SQL before having something better in its
place.
Access forces you to use a new workaround every single hour.
No argument there, but even with the workarounds it's still easier
overall to use and maintain than SQL Server. Unless you have a
situation where SQL Server has clear advantages over Access, and that
happens less often than you seem to think, it makes no sense to change
an existing Access application to SQL Server.
Linked table crap? NOT NECESSARY
BAD datatypes? NOT NECESSARY
I just don't get it.
You mean you don't get why we are not all flocking over to SQL Server
with Access as fast as our nimble fingers can take us there? Maybe
we're all incredibly stupid. If that's the case, you're wasting your
time trying to enlighten us anyway. Calling something stupid without
giving good reasons is out of vogue. Very Microsoft
. I seemed to
imply that I was calling Microsoft stupid without giving a reason, hence
the smiley. In case you need an explanation, I implied that Microsoft
marketing often resorts to name calling as a marketing tool. Actually,
I don't think Microsoft is stupid at all. They use marketing techniques
that work. It is simply unfortunate that name calling has been
effective so far. What we need from you is cool, concise, logical
reasoning. Do you feel up to it?
There isn't a single person in the world that should ever store any
credit card information in either
a) a spreadsheet
b) a database that is _IMPOSSIBLE_ to secure.
I agree.
Stop making excuses.
So sorry that your database SUCKS.
You're the one who's trying to dream up impractical situations to show
us why we should switch. There are good reasons to switch in some
situations, but you don't seem to know what the situations are or even
the reasons. The reasons you give seem trivial at best. There is a
good reason hidden in linked, bound tables, but your analysis has left
that reason unexposed. You seem to be struggling with the relative
importance of everything. Perhaps you have too little experience with
Access to be able to make good generalizations about it. That's
understandable if you have been putting most of your time into SQL
Server. At least you tried to come up with some valid reasons for your
last statement.
James A. Fortune
(e-mail address removed)
