somebody please tell me how I delete an ".LDB" file

[Matt]

You are the only one slamming anything man.

You just have what I, and most other people, would call "Communication
Issues"

Be a little nicer guy

 

[aaron.kempf]

be a little nicer guy?

I'm not going to compromise my values just because you kids are a bunch
of fat lazy slobs that can't adapt to existing technologies.

MDB is the most ridiculous platform ever; anyone anywhere using it for
any reason should be unemployed.

it's time that you kids- living in a clamshell-- woke up to reality.

MDB is crap; every little workaround that you do?
it's all a house of straw.

I build my house out of brick, prick.

-Aaron

 

[aaron.kempf]

why don't you stick with the facts.. ADP is the same price as MDB.

but you don't have the maintenance nightmares.

ADP is like a car that doesn't ever need it's oil changed or gasoline
topped off.
MDB is a tricycle with 2 flat tires.

-Aaron

 

[Matt]

youre a sad clown!

 

[Matt]

What do you think about Oracle chief?

 

[aaron.kempf]

you sit around and call me names

and you don't even argue the facts

what a lame ass kid you are; i'll make you a deal.
you tell me how to bind a form to a sproc in MDB and we'll compare and
contrast, ok?

 

[Matt]

how old are you

 

[aaron.kempf]

old enough to step on you, you little brat!

not old enough to be a senile old fart that is too stupid to learn SQL
Server and ADO.

-Aaron

 

[aaron.kempf]

what do i think about Oracle?

I dont think that Oracle is competitive; on price / performance.

On the other hand; I hope that MS gets it's ass kicked in the db world.

Microsoft isn't taking the db market seriously; and they never have.
ADP was the FIRST product to come out of Redmond that you could run
your whole business on.

It is reliable; it is scalable; it is easier development than MDB.

-Aaron

 

[William Hindman]

....my patience wears thin with your toddler temper tantrums ...with the
number of caustic posts you've made lately ...most of absolutely zero value
to the question asked ...I wonder when you find time to remove your head
from your ass long enough to create these works of wonder you so rapturously
describe ...most likely in your dreams, eh.

....lest you not be paying great attention, Microsoft has made it abundantly
clear that its front end development platform of choice for SQL Server is
not Access but a dotNet language ...the Jet database engine that drives
Access has been removed from the SQL Server development team and handed to
the Access development team for all future development ...read this comment
from the Access Development Team itself ...and then perhaps we can count on
you to shut up:

"The two weaknesses of ADPs that likely won’t be fixed because of the
underlying architecture include the inability to link to external data
sources (without setting up linked servers) and local queries. Combining
adhoc heterogeneous data sources is a big part of Access functionality that
is used heavily by most customers. The Access team is making a big
investment in using the Access Data Engine as the way to get to external
data sources. I expect that to continue in the future.

For new SQL Server projects where you are evaluating which platform to start
from, we recommend MDBs or ACCDBs with linked tables because they offer more
flexibility and that is likely where the Access team will invest the most
when building new features.

We have also found that applications that are upsized from mdb back-end
tables to SQL Server link tables require far less application changes than
upsizing to ADPs. The upsizing wizard defaults have been changed from
upsizing to ADPs to move the data to SQL Server and replace local tables
with link tables. In other words, the upsizing wizard will not default to
ADPs." http://blogs.msdn.com/access/comments/602128.aspx

....so tell us oh great ADP wizard, who's working with a "DED" database
format now, eh?

William Hindman

 

[aaron.kempf]

Dude

you're the biggest fucking retard I've ever talked to in my life.

A) NO NEED FOR LOCAL QUERIES YOU FUCKING RETARD
I MEAN SERIOUSLY-- WHY DO YOU 'NEED' LOCAL QUERIES

B) NO ACCESS TO EXTERNAL DATA EXCEPT LINKED SERVERS
1. what's wrong with linked servers, you fucking baby
2. DTS is a real tool; it's easy to develop a DTS package (using
SQL Developers Edition - $49) to move data from ANY other data source
to the central SQL Server; on a scheduled basis without writing any
code.

I mean seriously here.

Yes; .NET is a decent platform.

Does it have 1/10th of the ROI as Access Data Projects?? I THINK NOT.

Far less application changes?

So what; you can loop through queries; in order to update a
sql-passthrough.. but you can't afford to loop through queries and
rewrite them from JET-CRAP to REAL SPROCS?

the amount of funcitonality, performance is 10 times greater in Access
Data Projects than in your stupid little MDB files.

MDB is for fucking retards; I mean; what kindof fucking retard is still
using MDB files?

it's the most ridiculous thing that I've ever seen.

you're still workign with a DED database.

I can out-develop you on a free platform; with better scalability,
performance; and ease of administration.

I dont spend all my time copying 'local queries'

I mean seriously here.

What can you do with local queries that I can't do with sprocs?

I mean seriously; give me a list you fucking retard.

Lets start:

a) to update a sproc call in an MDB; you loop through DAO; a library
that has been DED for EIGHT YEARS??

b) in ADP; you don't need to write a single damn thing. It's all
simple binding; much simpler binding and much more powerful than
anything available in MDB.

how about running a whole bunch of queries:

a) loop through queries; using a piece of shit ass language; that only
retards and senile dipshits from Canada care about

b)

create procedure mysproc;1
as
update myTable Set Val1 = 'A' Where Val1 = 'Y'

create procedure mysproc;2
as
update myTable Set Val1 = 'B' Where Val1 = 'Z'

create procedure mysproc;3
as
update myTable Set Val1 = 'C' Where Val1 = 'X'


and then if you want to fire all three of them; it's

exec mysproc

ok lets try this one:

a) what do you do when you walk in as an MDB developer
1. susies comes up; she can't open the app because george has it
opened exclusively by accident
2. you need to compact and repair a bunch of database files; so yuo
email accounting and ask them to get out of the database so that you
can compact / repair and you can take a backup.

b) what do i do when I get in?
1. DEVELOPMENT
2. OPTIMIZATION


So seriously here; who gets more done, you or me?

Does my platform cost a DIME MORE than yours?

NO.

If I want 100 times as much functionality; to run multi-threaded ETL
apps-- then I can spend $49 to buy a developers copy.

What do you do when susies comes up and she wants to report out of the
database from a web platform?

a) susie, I'm sorry I CANT PHYSICALLY USE MDB DATA FOR WEBSITES
b) Aaron, the ADP developer says 'oh yeah; I've already got a web
interface for you'

What do you do when you deploy a new app
a) loop through a bunch of queries, pushing out 100 different copies of
the same query to 100 different desktops.. (HOW DO YOU DIAGNOSE WHEN
JOHNNY CHANGES A QUERY AGAIN?)

b) uh change a sproc and it's already deployed.

MDB is for cripples and babies.

People with learning disabilities.

Access Data Projects are a better, easier, more dependable solution.

Every customer I've ever had says 'oh, i dont need to worry baout
database performance' - it's like their scared of saying 'hell yes make
it fast'

I CAN OUT-DEVELOP ANY MDB DEVELOPER ON A MORE SCALABLE PLATFORM THAT IS
THE SAME COST.

bunch of fucking retards.

you take shit from Microsoft so far out of context.

Microsoft is supporting Access Data Projects.. ADP is not going away--
they have continued to develop ADP throughout the past decade...

And you really believe that all of a sudden that they'll just change
direction?

Conflicting reports coming from informal sources.

Access Data Projects kicks the living shit out of your stupid ass
spreadsheets and mdbs.

Stick a fork up your ass and screw yourself.

MDB is DED and ADP is here to rule the day.

-Aaron

 

[William Hindman]

....my, my, my ...hit a nerve did we ...got the toddler all in a rant
....yelling even ...and expletives yet ...and yet when I quote the Access
Development Team and give you a link, all you can do is scream unsupported
opinions and expletives and call them retards

....hhhmmm ...hey, Aaron ...guess which retards are making the decisions on
Access without your input, eh?

....well ta ta Aaron ...you be a good little toddler now

....I'd like to say its been fun, but it hasn't ...mostly boring, like
playing with a sick kitten.

....my work here is done.

William Hindman

 

[aaron.kempf]

that's not a direct quote from the Access team.

you paraphrase it.

I'm not a toddler; and my career _SURE_ isn't tied to Access any
longer.
Yes; I use it every day-- I use it in the same way that normal dipshits
use Excel and Word.

MDB is still for babies; I get shit done while you kids run around with
workarounds; crappy performance and COMPACT AND REPAIR?

ROFL

Just because ONE DEVELOPER reccomends that you use Linked Tables for
ACCDB; that doesn't mean that it is the official view of Microsoft; nor
of the whole team.

And just because one fat, lazy Access developer is too stupid to learn
SQL Server; does that mean that we all should run away; throw away
Oracle / SQL and screw around with MDB?

ROFL

MDB is for sick kittens.

Retards that can't learn SQL.
Access Data Projects allows you kids to spread your wings; to grow out
of a career-limiting application.

That is why there aren't more ADP people around here.
REAL ADP PEOPLE GROW A LIFE; GET REAL JOBS.

Dorky MDB kids still worry about compact and repair?

ROFL

eat shit, bud

ADP rocks. I can out-develop _ANY_ MDB developer anywhere in the
world.. on a platform that is JUST AS FREE; it is 10 times more stable
/ scalable; and SQL will be around 20 years from now.

MDB won't.



-Aaron

 

[William Hindman]

....sad to say that it is ...and from the team leader himself ...its their
official blog site.

....and I can only judge you by your ng postings ...which definitely makes
you a toddler

William Hindman

 

[Klaus Oberdalhoff]

Hi,

...sad to say that it is ...and from the team leader himself ...its
their official blog site.

...and I can only judge you by your ng postings ...which definitely
makes you a toddler

I looked for the german word "Trotzphase" (a child in his ...)
and got (www.leo.org)

the terrible twos [psych.]

Doesn't this describe it better ? <LOL>

Klaus

 

[William Hindman]

....lol ...precisely

William Hindman

Hi,

...sad to say that it is ...and from the team leader himself ...its
their official blog site.

...and I can only judge you by your ng postings ...which definitely
makes you a toddler

I looked for the german word "Trotzphase" (a child in his ...) and got
(www.leo.org)

the terrible twos [psych.]

Doesn't this describe it better ? <LOL>

Klaus

 

[aaron.kempf]

a toddler?

only a dipshit toddler would continue investment in a platform that has
proven itself TOO UNRELIABLE.

Access MDB?

Do you seriously think that it's efficient to ask NEWBIES to learn 2
different SQL dialects?

ROFL

Access MDB is for cripples and retards.. and if you continue using it--
you need to come out and say 'yes; I am a crippled senile retard that
JUST DOESNT HAVE THE MENTAL CAPACITY TO REALLY LEARN SQL SERVER'

that's what it's all about

you dipshits aren't SMART ENOUGH to learn SQL Server. because if you
really knew how to use SQL Server; you wouldn't want ANYTHING to do
with MDB.

Have you ever looked at profiler and what happens with a linked table?

ROFL

what a piece of shit ass language; buddy.
MDB is DED.

Access Data Project is 100 times more reliable, more dependable; and
more scalable.

Just because one INTERN on the Access team reccomends that they use
linked tables; does that mean that it is the official view of
Microsoft?

is Access Data Project not going to ship-- because this DIPSHIT thinks
that MDB is cooler?

WHAT THE **** IS UP WITH YOU KIDS

OH, I NEED LOCAL QUERIES

ROFLMAO

OH, I NEED LOCAL QUERIES

WHAT THE ****?
WHY THE FLYING **** DO YOU DIPSHITS THINK THAT YOU NEED LOCAL QUERIES?

WHAT YOU NEED; IS YOU NEED MSDE ON YOUR DESKTOP.

Hi,

...sad to say that it is ...and from the team leader himself ...its
their official blog site.

...and I can only judge you by your ng postings ...which definitely
makes you a toddler

I looked for the german word "Trotzphase" (a child in his ...)
and got (www.leo.org)

the terrible twos [psych.]

Doesn't this describe it better ? <LOL>

Klaus

 

[aaron.kempf]

and while you're at it; why don't you STFU

if you had ANY balls your granddaddies would have kicked the shit out
of the Soviet Union during WW2.

you are bigger pussies than the french.

fucking pussies can't even beat a couple of dipshits on horses.
fucking pussies can't learn SQL Server

eat shit you fucking pussy ass germans

Hi,

...sad to say that it is ...and from the team leader himself ...its
their official blog site.

...and I can only judge you by your ng postings ...which definitely
makes you a toddler

I looked for the german word "Trotzphase" (a child in his ...)
and got (www.leo.org)

the terrible twos [psych.]

Doesn't this describe it better ? <LOL>

Klaus

 

[Klaus Oberdalhoff]

*PLONK*

 

[aaron.kempf]

well seriously buddy

you tell me how much time you spend compact and repair.. how long did
it take you to understand these concepts when you were just starting.

why is it that you need to RELINK _AND_ REFRESH?

wtf is up with that?

how do you backup your mission critical databases that are built on
MDB?

EVERY database should allow itself to be mission critical; even if it's
a simple list of customers.

solutions built on MDB are short-lived; they don't scale.. they don't
even fucking run over the network well.

i mean.. have you ever had to enter data into a mdb across it network?

it takes FRIGGIN FIVE SECONDS TO OPEN THE DAMN APP

what a piece of shit; there isn't anything in the world that should
take 5 seconds to do.

-Aaron