switched from Novell to Citrix now keeps getting corrupt

[Todos Menos [MSFT]]

a) no; SQL Server does _NOT_ do the same thing on a linked table as
ADP. ADP returns the results; MDB does a SCAN in most situations.
b) MDb doesn't support triggers == MAJOR REASON TO NEVER USE MDB FOR
ANYTHING ==
c) ADP allows simple binding to a sproc _WITH PARAMETERS_ that is
completely superior to Access MDB parameter queries. If you've got a
sproc parameter named '@txtplu' it will bind to the control txtPLU.

NO CODING NECESSARY

with MDB if you want to use a form on a sproc; it requires a sql
passthrough and about 100 lines of code

TRY ARGUING WITH THE FACTS, KID

 

[Todos Menos [MSFT]]

re:
What are you *talking* about? An ADP is only an option if you're
using SQL Server as your back end. You seem to be completely
confused about the nature of Access as both front end and back end.

yeah of course I know that.
SQL Server is the only decent 'backend' for MS Access
I mean DUH!


re:
No, it doesn't. The quotation, which is from MS's current Office
2007 documenation website, clearly states that there are exactly the
same number of layers involved.


I don't care if Jesus Friggin Christ came down and stated this as
fact. IT IS NOT TRUE. ADP = ONE LAYER. SQL SERVER.


re:
Who cares? This has zilch to do with the issue, because we're
talking about MDB vs. ADP for a SQL Server back end, so that fact
that SQL Server has this means nothing, as it's present in both
cases.


this has nothing to do with the issue?
MDB IS NOT AN OPTION DUDE OF COURSE IM TALKING ABOUT SQL SERVER. MDB
LINKED TABLES TO SQL SERVER?


ROFL
ROFL
ROFL
ROFL

DUDE YOU ARE JSUT A FRIGGIN DIPSHIT AREN"T YOU?

YOUR FUD DOESN'T WORK AGAINST ME
MDB IS MOTHER FRIGGIN CRAP KIDS

 

[Todos Menos [MSFT]]

re:

b) SQL Server has 'index tuning wizard' and 'database tuning
advisor'

Who cares? This has zilch to do with the issue, because we're
talking about MDB vs. ADP for a SQL Server back end, so that fact
that SQL Server has this means nothing, as it's present in both
cases.

I'm sorry... but WHO CARES?

WHO CARES?
I DONT HAVE TO DEAL WITH INDEXES; BECAUSE I DON"T SPLIT MY APP INTO A
FRONT END AND A BACKEND-- YOUR MDB HAS DUPLICATE INDEXES, WASTED
SPACE-- FOR DATA AND INDEXES

I INDEX IN ONE PLACE

YOU POORLY INDEX IN TWO PLACES

stick a cork in it kid


'oh only if i use sql server'

yeah no mother ****ing shit dude

ADP kicks MDB's ass

I'm sorry that you don't have the capacity to grow past the 1st grade.

MDB IS FOR RETARDS; IT IS NEITHER STABLE NOR RELIABLE

 

[Todos Menos [MSFT]]

Re:
MDBs may cease to exist, but they will be replaced by ACCDBs,
instead, which is just an extended version of the MDB utilizing the
forked Jet 4 database engine.



I've got multiple public posts from Microsoft where MICROSOFT STATES
THAT MDB HAS BEEN OBSOLETE FOR 10 YEARS.

ADP is alive and well. ADP has been improved with every release for
the past decade.
MDB hasn't even gotten simple bug fixes


MDB is crap dude; you're an idiot if you use it.

TO THE WORLD:
if you have some idiot like David Fenton working for you? In other
words _ANYONE_ using MDB for anything?
FIRE THEM AND THEN SPIT ON THEM