Database Connectivity

[rowe_newsgroups]

VB.net has a negative ROI.

By ROI I assume you mean return on investment? If so on what are you
basing this on?

Access Data Projects; things are SOOOOOO much easier

In my opinion ADPs are not nearly as powerful or as secure as a .Net
solution. Also, using ADPs limits you to SQL Server, limiting which
database systems you could use in the future. (As from what I
understand, the OP's company isn't using SQL Server and may prefer a
different db solution like Oracle).
Some other big benefits of using .Net over Access is the that Access
isn't required on each computer, and you have the option to devolop
solutions on mobile devices.

So Ivan, just remember to think about what the project might devolop
into, and don't limit yourself to a certain set up.

Thanks,

Seth Rowe

Learning VB.Net also means that you don't

 

[Guest]

Access Data Projects; things are SOOOOOO much easier

And harder to maintain too.

 

[Anon-E-Moose]

By ROI I assume you mean return on investment? If so on what are you
basing this on?

Don't mind Aaron Kemp - I think he's the nutcase of the group ; )

 

[Guest]

Would you recommend going with the controls built into Visual Studio,
coding within the subs as I need them, or creating a class to handle all
of my database connectivity.

I am guessing a class is the best way for code re-usability but how
would I go about keeping it generic?

Check out LLBLGen for your data layer - they basically provide .NET 3.0
LINQ, OR/M features now ;-)

 

[aaron.kempf]

BS; harder to maintain?
You keep everything in one place!!!

well shit let me just come out and say that .NET causes AIDS.

no facts; i'll just run out and make a claim; ok?

-Aaron

 

[aaron.kempf]

re:
In my opinion ADPs are not nearly as powerful or as secure as a .Net
solution. Also, using ADPs limits you to SQL Server, limiting which
database systems you could use in the future. (As from what I
understand, the OP's company isn't using SQL Server and may prefer a
different db solution like Oracle).
Some other big benefits of using .Net over Access is the that Access
isn't required on each computer, and you have the option to devolop
solutions on mobile devices.


your opinion is wrong.

ADP limits you to SQL Server? SQL Server rules the roost; you're a
****ing idiot if you haven't looked at tpc.org in the past decade.

and you're really; honestly going to use a toolset that takes 3 times
as long; just so that you can put it on a PDA?

get a ****ing clue; kids

Mobile is worthless.

ADP runs circles around you kids.

And he should take his Access experience and apply it to Access Data
Projects.

I would rather use a CSV file than MDB.

-Aaron

 

[Izzy]

Aaron,

You really should stick with the Access group, you're in love with
Access and completely blinded by love.

It's fine, and sometimes your actually even helpful there.

People who post questions in the .NET group really don't benefit from
your input. They are not going to convert to ADP just because Aaron
says so. You need to go lay on someone's couch and talk about your
frustrations.

Izzy

 

[aaron.kempf]

well the kid was talking about using access.

****ing jackass; nobody should use the MDB file format for ANYTHING.
It's not scalable; its not reliable.

It's almost as bad as using Excel.

If he's a friggin loser that uses Access MDB as a database; he might as
well be using Access forms and reports.

-Aaron

 

[aaron.kempf]

oh YAH

LINQ, OR/M

It would help if you knew how to use SQL Server you friggin jackasses
If you're looking for an easy solution to a real database-- use Access
Data Projects.

I can out develop any of you .NET kids on performance, features, price
and performance.

-Aaron

 

[Guest]

It would help if you knew how to use SQL Server you friggin jackasses
If you're looking for an easy solution to a real database-- use Access
Data Projects.

I can out develop any of you .NET kids on performance, features, price
and performance.

Why rewrite the data layer EVERY time?

Not to mention you'll make mistakes in the SQL - (generated) data access
layer save you from all the hassles.

You still need to know how T-SQL, SQL Server, and Database design ... but
OR/M mappers save you the mundane chore of filling data objects

 

[Guest]

****ing jackass; nobody should use the MDB file format for ANYTHING.
It's not scalable; its not reliable.

No need to swear! I've read what you post... and a lot of it make sense -
but you come on too aggressively.

Yes, MDB sucks for the most part... but there are situations were it does
make sense - for example small desktop apps that need localized storage. Of
course no one in their sane mind should use MDBs for enterprise/scalable
apps.

If he's a friggin loser that uses Access MDB as a database; he might as
well be using Access forms and reports.

 

[aaron.kempf]

rewrite the data layer? ROFL

use client-server not 3-tier dude

you're bitching that 'everyone makes mistakes in sql' but i sure
friggin dont make mistakes in sql.

why would you spend 90% of your time writing code that is 3 times as
verbose as what it takes in Access Data Projects

I can out develop you kids; you kids should stop taking marketing crap
to heart and get some real-world experience.

OR/M?

i mean seriously.

WTF are you talking about jackass

 

[aaron.kempf]

small desktop apps that need local storage?

lose the training wheels; bud

why do people NEED local storage?

it's the stupidest idea ever.

give people SQL on the desktop if you MUST lol

 

[Izzy]

I can out develop any of you .NET kids on performance, features, price

and performance.

First learn to type good sentences and then we'll talk about
developing.

Something else you should try and grasp, when you swear and call people
names that doesn't harden your position or make it more right. It makes
you seem ignorant; therefore everything that follows is disregarded.

Wise up man!

 

[aaron.kempf]

more importantly

why re-invent the wheels

binding forms to a database table or sproc?

INSERT, AUTOFORM, DONE.

why build OBJECTS?

i've got all the objects I need already.

Lose the training wheels; the action is in the database world; and no
amount or OR/M _CRAP_ is going to save you.

-Aaron

 

[Guest]

small desktop apps that need local storage?



why do people NEED local storage?

give people SQL on the desktop if you MUST lol

What a hassle to load MSDE type engine.

 

[Guest]

why build OBJECTS?

i've got all the objects I need already.

Lose the training wheels; the action is in the database world; and no
amount or OR/M _CRAP_ is going to save you.

So you build new applications? haha.

 

[Guest]

you're bitching that 'everyone makes mistakes in sql' but i sure
friggin dont make mistakes in sql.

I guess you must be god.

 

[aaron.kempf]

what SMS or Active Friggin Directory could push it out; without any
intervention.. in probably 60 seconds

-Aaron

 

[aaron.kempf]

I just find it laughable.

shit; if you don't want to put MSDE on the desktop; then put it on some
unused desktop and use it for a dozen people.

definitely a better solution than hosing up a whole file-server just
because you're playing with a tool for babies.

MDB chokes networks; file servers-- MDB isn't reliable.

you're ****ing retarded if you use MDB for anything.

and if you already know Access?

you can get more done; against SQL Server-- using Access Data Projects
than your red-headed stepchild of C#

Microsoft killed the most popular language in the world; get over it.
Go back to using Access.

-Aaron