mdb to adp

[Guest]

I've converted my Access Database to Access Project (mdb to adp) but problem
is this that some queries and sql written in code is not working. Please
advice me.

 

[Larry Linson]

I've converted my Access Database to Access
Project (mdb to adp) but problem is this that
some queries and sql written in code is not
working. Please advice me.

To what purpose did you convert? The only reason I know to make such a
conversion was the assumption that ADP worked better with linked MS SQL
Server tables. That seems not to be the case, as the Access development team
now recommends MDB-DAO-Jet-ODBC-MSSQLServer as the method of choice over
ADP-ADO-ADODB-MSSQLServer.

The queries and SQL use slightly different notation because they are are
using OLEDB -- it's more like the MS SQL Server "dialect" of SQL. (Actually,
I think it IS the SQL Server dialect, but there may be some minor
differences.) Did you make a conversion thinking that there would not have
to be any manual modifications?

Larry Linson
Microsoft

 

[Guest]

Using DAO in mdb file is slower than OLEDB/ADO thats why i choose adp.
actually i have a project which is supposed to be run over WAN/VPN,
nation-wide. For this purpose i prefere to use DB Server rather than file
sharing topology. I have tried both by making DSN file and creating a link
using OLEDB/ADODB and I found adp is a faster and better option as using DSN
file on mdb found slower. Please advice further.

 

[Larry Linson]

Using DAO in mdb file is slower than OLEDB/ADO
thats why i choose adp. actually i have a project which
is supposed to be run over WAN/VPN, nation-wide.
For this purpose i prefere to use DB Server rather than file
sharing topology.

I'm sorry if I misled you -- I certainly did not suggest using a split
Access-Jet database in that situation. I suggested using MDB - DAO - ODBC -
MS SQL Server, which with good design for the client-server environment, has
served me well with several different Server databases. I could see no
worthwhile speed improvments in the ADP environment in which I did some
work.

I have tried both by making DSN file and creating a link
using OLEDB/ADODB and I found adp is a faster and
better option as using DSN file on mdb found slower.
Please advice further.

When you say "by making DSN file", I assume you mean "using ODBC drivers" to
compare speed against the OLE DB approach using ADO. If you have done an
extensive comparison and found it sufficiently faster to be worth the bother
in your environment, who am I to suggest you do otherwise?

To the best of my knowledge, I answered your original question. For details,
in Access 2003 in the Database Window, go to Help, choose Microsoft Access
Help, search for "Jet SQL", then in the list of topics, choose the article
entitled "Comparison of Microsoft Jet SQL and ANSI SQL" and then also read
the article entitled "Access projects and data access pages now use ANSI
SQL-92 Syntax."

Larry Linson
Microsoft Access MVP

 

[aaron.kempf]

larry

you are full of shit dude

ADP is 100 times simpler and better in every possible manner

how do you bind a form to a sproc in MDB? with a half dozen
parameters?

PLZ enlighten us or STFU

I know in ADP it takes _ZERO_ code

and if you sit there and say 'uh, what's a sproc' then i'll say SHUT
THE **** UP AND DONT YOU EVER SPREAD _LIES_ ABOUT ADP EVER AGAIN

bullshit ass mother ****er, too lazy to learn SQL Server-- STFU before
you get yourself in trouble, old man

-Aaron

 

[aaron.kempf]

a) ADP _IS_ faster
b) ADP _IS_ **EASIER**
c) ADP _IS_ MORE POWERFUL

lose the training wheels, Larry I'm sick and tired of you spreading
BULLSHIT ASS LIES

ADP is faster in everything that you do

-Aaron

 

[aaron.kempf]

and for the record, Larry

your MDB _CRAP_ can't run over a WAN in _ANY_ way, shape or form.

NO WE DO NOT NEED TERMINAL SERVERS.

**** YOU OLD MAN; GO AND PLAY IN THE SNOW

THE RESOURCES THAT ARE AVAILABLE FOR ADP DEVELOPMENT OUTNUMBER _ALL_
MDB RESOURCES BY A FACTOR OF 10 TO 1.

ANY CLASS ON SQL SERVER MAKES YOU A BETTER ADP PROGRAMMER.

MDB has been obsolete for _TEN_ YEARS

-Aaron

 

[aaron.kempf]

ADP has no compact / repair
ADP has no bullshit 3rd later of security that _SUCKS_
ADP has no linked table manager

ADP doesn't need a bullshit 'AUTO FE UPDATER' because all the queries
live on the database server-- WHICH IS WHERE THEY BELONG

ADP is an awesome tool; I reccomend it for people new to SQL Server,
Sr SQL Server people.. I reccomend it to everyone.

I just hope you're not scared away cuz this SENILE RETARD doesn't know
how to _SPELL_ TSQL

-Aaron

 

[aaron.kempf]

'worth the bother' = LESS WORK for ADP development

seriously larry

go home and talk to your bitch ass grandma and stfu and stay out of
the grown mans' discussion

ADP rocks and I'm not going to let you talk shit about it for any
longer.
it _IS_ faster, it _IS_ easier

lose the training wheels you ****ing retards

MDB IS DEAD

-Aaron

 

[aaron.kempf]

some queries need to be rewritten

I've written scripts to automate most of it.. it's really not that
difficult

give me some examples of what's not working; and I'll do my best to
help

-Aaron
SQL 2005 Certified