[AccessD] Learning .Net

I love this line:
 I have not seen any "earth shattering" advances to
spread/work sheet and database concepts since their original design,
only silly bells and whistles.

But really, it should read:

 I have not seen any "earth shattering" advances to
spread/work sheet and database concepts since their original design,
only silly bells and whistles and incompatibility between versions.

:)



I would say learning SQL server would be an easier transition.

You can learn Oracle after you are comfortable with SQL server.

D

On Mon, Jun 22, 2009 at 10:14 AM, Tony Septav <iggy at nanaimo.ark.com> wrote:

> 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
>