[AccessD] Learning .Net

Not Oracle?  Yikes!  <grin>

As an ardent fan of Access (especially Access 97), I must admit that
knowledge in a server side database can come in real handy!  On a normal
network, an .mdb solution works fine, but try using it over a VPN, and
yikes..... 

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav
Sent: Monday, June 22, 2009 12:15 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Learning .Net

Hey All
Like many of you on this list I have to admit I am an old fart. Must 
mention that I deal with small to medium sized netwroked businesses. As 
has been stated it is hard to "teach an old fart new tricks". Like many 
of you I realize that I have to learn SQL Server and .Net or go the way 
of the dinosaur. But to me that is playing into the industry marketing 
"flavour of  the day". Other than the IT Borg saying it will not put 
your ACCESS application on our system, I don't really see how it matters

what language you use.  If you produce a fast, user friendly application

that is easy, intuitive and bullet proof for the user, who cares. If the

industry marketers would allow I could still use Lotus 123 for DOS to 
develop number crunching spreadsheets that 80% of the users would be 
quite content to use because it produces the results they are looking.  
Same with ACCESS, I still have 97 Apps out there being updated and 
working fine.  I have not seen any "earth shattering" advances to 
spread/work sheet and database concepts since their original design, 
only silly bells and whistles.
I could be wrong and I know many of you will set me straight.
Why SQL Server and not Oracle?????
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.