When to Move to SQL Server?

[aaron.kempf]

how can 2 people write queries at the same time?

I mean seriously here

please explain

you need 'open exclusive' to do that.. right?

 

[aaron.kempf]

it's not a question of whether something is 'new' or not

it's a question of learning to speak 2 languages.. or learning to speak
1 language.

Access-SQL is obsolete; SQL Server is bigger, better, faster

and if you think that it's cheaper to develop in Access than SQL; that
just means that you're delusional

 

[aaron.kempf]

I'm not saying 'dont use access'

im saying 'dont use mdb'

Access is the best platform in the world-- i'll be the first to admit
that.
I can out develop any MDB develop using SQL Server..

i Mean.. if Access MDB had 'Query Analyzer' where you could write a
whole bunch of queries at the same time?

then it might be competitive

I love your stories.

Im not reccomending that people use .NET and Oracle.
I'm reccomending that they use the FREE MSDE or SQL Express.. and
Access Data Projects.

I can out develop you MDB pussies any day of the week in ADP

it's not that im smarter; it's not that im more disciplined.

I just listened to hundreds of people that bitched when their
applications took a minute to open.. and i realized that MDB is
obsolete and it has been for a decade

I have developed $1000 ADP solutions.
I have developed $10,000 ADP solutions.
And I have developed $50,000-$200,000 ADP solutions.

I don't need to rewrite everything once I get a half dozen users.

I've seen more Access MDB in the real world-- than all you stupid
monkeys combined.
And I; for one-- am sick and tired of being called in at 2am when
somebodys' truck can't leave the factory because a picklist is having
locking problems.

Im sick and tired of sending out emails; asking everyone to 'get out of
the application so that I can add a column'

I mean; your crap is laughable; MDB is obsolete

 

[aaron.kempf]

and for the record; I built a $12,000 ADP solution that some MDB
dipshit tried to rewrite in MDB and he spend $93,000 trying to convert
it but FAILED.

I've built ADP solutions that replaced a 'million dollar spreadsheet'

I've built ADP solutions that scale to over 100 users over 10 different
locations; including replication and awesome reporting capabilities.

I've built ADP solutions that help you to get your morning espresso
I've built ADP solutions that helped in the testing of Windows XP SP2
I've built ADP solutions that helped secure the worlds largest computer
network.

Does MDB scale past a half dozen users?

NO.

I don't need to rewrite my shit when my apps get more powerful.
And I don't cost a dime more than you stupid MDB pussies.


-Aaron

 

[aaron.kempf]

my dumptruck isn't any more expensive than your VW golf.

my dumptruck gets BETTER MILEAGE than your VW golf.

and my dumptruck doesn't crap out when 2 people try to ride in it at
the same time.

 

[susiedba]

Access can't allow 2 people writing queries at the same time.. right?

I wish it would; we have a lot of team projects around here and it
would be nice if Access MDB had basic multi-user functionality

 

[(PeteCresswell)]

Per (e-mail address removed):

Access can't allow 2 people writing queries at the same time.. right?

I wish it would; we have a lot of team projects around here and it
would be nice if Access MDB had basic multi-user functionality

You need to split the app into two .MDBs: One for the front end with ODBC links
to the other, which will be the back end.

Then you deploy a copy of the front end to each user and everybody's happy...

 

[susiedba]

NO.. PETE

this doesn't help me to write queries at the same time.
this helps me to write 2 queries into 2 different databases.

THEN WHAT?

HOW DOES SUSIE SEE AARONS QUERY?

your split front-end back-end bullshit is unacceptable.
it is a waste of time; it makes management TOO COMPLEX.

I don't make people copy stuff to their desktops-- and I don't deploy
40mb frontends.

Access Data Projects are just EASIER FOR DEVELOPMENT, DATA ENTRY,
ADMINISTRATION, AND MAINTENANCE.

Anyone that tells you otherwise is a FAT SENILE LOSER THAT DOESNT HAVE
THE MENTAL CAPACITY TO LEARN SQL SERVER.

with an Access Data Project; Susie can write a QUERY AT THE SAME TIME
THAT AARON CAN

I dont want to 'sync my queries'

I dont want to 'use visual source safe'

I just want 2 people to be able to share queries.

MDB is for lepers and retards you losers need to wake up to reality



-Susie

 

[(PeteCresswell)]

Per (e-mail address removed):

NO.. PETE

this doesn't help me to write queries at the same time.
this helps me to write 2 queries into 2 different databases.

THEN WHAT?

HOW DOES SUSIE SEE AARONS QUERY?

your split front-end back-end bullshit is unacceptable.
it is a waste of time; it makes management TOO COMPLEX.

Your writing style seems very similar to Aaron's....-)

 

[susiedba]

yeah your fat lazy senile ass seems just like Larry Linson

 

[aaron.kempf]

please pete.. please tell me how 2 people can write queries in the same
database

I'm dying to find out

you see.. there are these things out there called 'companies' that
typically hire more than 1 person??

It just seems like it's one of those things that you can't get around.

UNLESS YOU USE ACCESS DATA PROJECTS

 

[(PeteCresswell)]

Per (e-mail address removed):

please pete.. please tell me how 2 people can write queries in the same
database

Never tried it. Never want to bc that would imply two users
opening up the same front end at the same time. Wouldn't
think about that any more than I'd think of ways for two people to open the same
executable at the same time.

Now *to* or *against* the same DB, no problem....

 

[aaron.kempf]

so what you're saying is this.

ACCESS DOESNT SUPPORT MULTIPLE DEVELOPERS

no wonder you kids as losers and loners


Access Data Projects _SURE_ dont have this problem

 

[aaron.kempf]

what.. do susie writes queries to db1 and aaron to db2.. and then you
sit there and sync the queries by hand?

ROFL

how many queries DO YOU WRITE?


it's just not worth the overhead; MDB is a pain in the ass

 

[David W. Fenton]

Per (e-mail address removed):

You need to split the app into two .MDBs: One for the front end
with ODBC links to the other, which will be the back end.

Then you deploy a copy of the front end to each user and
everybody's happy...

While that's certainly true, the limitation on editing applies only
to Access objects, i.e., forms/reports/etc. It does *not* apply to
tables and queries. I just tried it -- I opened two instances of the
same MDB and created and saved a query in each instance. But it
would not allow me to edit an existing form or create a new one. It
would allow me to create and save new tables, and rename and
delete/recreate linked tables.

The reason for this, I'd guess, is that it's the Access project part
of your MDB that's stored in the BLOB in a single record (the
monolithic save model). This is why tables and queries retain their
CREATED and MODIFIED dates, whereas forms/reports/etc. always have
the date of the last compile and save.

What I don't really understand is why MS chose to not just use
MSysObjects to keep track of the dates created and modified for
Access objects. That part has always confused me, since that table
tracks that information for the tables and queries, too.

 

[David W. Fenton]

Per (e-mail address removed):

Never tried it. Never want to bc that would imply two users
opening up the same front end at the same time. Wouldn't
think about that any more than I'd think of ways for two people to
open the same executable at the same time.

Now *to* or *against* the same DB, no problem....

No one but the inexperienced (who don't know better) and complete
morons (who refuse to acknowledge the reality of how many huge
problems are caused by sharing a front end) will ever run multi-user
apps in anything other than a split configuration.

For sharing queries, this is what you do:

1. let people create queries in their front end.

2. tell them to use a naming convention that will identify the
queries they want shared with everyone.

3. provide a point and click method to export their queries to the
development copy of the front end (i.e., the one the developer uses
to make changes to the front end).

4. optionally, have a point and click method for importing any new
queries from the development copy of the front end.

You can do this for any kind of object. The key point is that the
objects have to be stored somewhere in an MDB that isn't being
shared.

But to tell the truth, I've proposed this to many a client, and
nobody thought it was worth doing! Most of them just maintain a
scratch MDB for this kind of thing because most of their ad hoc
queries aren't things that others would find useful.

 

[larrylinsonjr]

Access MDB should be migrated to ADP with ONE USER and a SINGLE RECORD

Any use of MDB is ridiculous; it has been obsolete for 10 years


-Larry

 

[aaron.kempf]

ACCESS HAS _NO_ MULTI-USER CAPABILITIES

And for the record; splitting into a frontend and backend-- it takes
away ANY advantage that MDB has over ADP-- that of portability

-Aaron

 

[dbahooker]

YET?

Access MDB is obsolete; it's not even included in the next version of
Access

 

[dbahooker]

YES. Speak English or DIE

(e-mail address removed) wrote in
obsolete?