Re: From .mdb to .adp database

I am currently experimenting with upsizing a front end/back end Access 2000
database and have found that keeping the front end an mdb with the back end
converted to SQL Server 2000 results in excruciatingly SLOW execution speeds
for the queries. As I understand it, this is because the queries (about 50 of
'em) are being executed on each workstation, not the server. Some of these
queries are pretty complex, but they are essential for most, if not all, of
the reports and forms to function correctly.

So I am now testing upsizing to an adp file. Only about half of the queries
made the migration successfully, but preliminary testing of the functions
that do work indicates that the adp approach will result in much faster
response times for the user.

HOWEVER, I am concerned about the posts that are suggesting Microsoft is
dropping support for adp. One of the reasons I have been asked by the Powers
That Be to upgrade the database is to allow for future growth. I'm not sure I
can claim that adp is the future. Are there any alternatives to adp that will
allow me to put the queries on the server without having to learn a
completely new programming environment, and which will enjoy future support?
THanks!

"Norman Yuan" wrote:


"Nesta" <nestaman@xxxxxxxxxxx> wrote in message
news:u9lMJpnEIHA.748@xxxxxxxxxxxxxxxxxxxxxxx
Hi Norman,

Thank you very much for your response.
I understand how things work better now.
Because i'm used to work with mdb files, it was difficult for me to
understand that ADP files are just an interface that is not directly
connected with databases, like it is in mdb (for example, the queries).
The reason why i got interested into ADP files is that i'm trying to find
the best way (with less changes to do ans without great changes in
interfaces) to convert my mdb into SQL.
But, as you say ADP is dying, maybe this way is wrong.
I know i can convert my tables and stuff into SQL and still use mdb
interface (by changing the link of the bases), but if i want to


Yes, the is what MS recommended: use MDB front end agianst SQL Server back
end, rather then ADP.
And yes, you need to use ODBC to link tables in SQL Server database. Whether
you use ADP or MDB, you need to set up connection to SQL Server database
anyway. For ADP, the connection setup is just marginally easier than MDB.

redistribuate my application, i will have to create the dbo connection on
every computers, isn't it ?
Do you have a better solution ?

Thanks by advance.

Nesta


"Norman Yuan" <NoAddress@xxxxxxxxxxxx> a écrit dans le message de news:
%23Xr2UEcEIHA.3332@xxxxxxxxxxxxxxxxxxxxxxx
ADP file, not like MDB, does not contains query. The queries you see in
ADP file are SQL Server objects (Views, Stored Procedures and UDFs...).
When converting, the queries in MDB may or may not be converted to
corresponding SQL Server objects, depending on what is in the mdb
queries. In your case, your query was conerted as stored procedure, which
sits in SQL Server back end, and has no knowledge of your ADP front end
(and it should not be tied to any specific front end at all), so the
conversion smartly enough to a sptored procedure and converted the two
required inputs as input parameters. Now, when you call this stored
procedure in an front end application, such as ADP file using it as a
form's data source, you need to get user input and pass the input as the
stored procedure's parameters.

If you already have an Access application done in MDB file, the better
approach would be to only convert data back end to SQL Server, and still
use your MDB front end, with possible minor modification. After all, ADP
type of application is dying.


"Nesta" <nestaman@xxxxxxxxxxx> wrote in message
news:ul6lgVaEIHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I'm testing migration from Acess database to ADP Project.
I have this query wich criteria of selection is the value of a textbox,
in a form.
In my mdb database, the syntax was like :
[Forms]![F_MyForm]![MyTextBox].

In my ADP project, i have noticed theses changes :
- my query was transformed into a function ;
- the syntax ro reach the value of my TexBox has changed (and obviously
does not work) : = @Forms_F_MyForm_MyTextBox.

1) How to find the good syntax ?
2) Where can I find ressources on ADP syntax ?


Thanks by advance !

Nesta







.

Relevant Pages

  • Re: Upsizing design considerations
    ... reports, with a ADP, or mdb (actually, it should be mde, or a ADE when you ... you would LINK the tables to sql server, and NOT USE a adp (the reasons is ... the first two remote users ...
    (microsoft.public.access.gettingstarted)
  • RE: database options with SBS 2003 R2
    ... It was doable for the customer to design their own access database in a peer ... If you don't want to deal with a version of SQL Server for the data, ... end MDB files. ...
    (microsoft.public.windows.server.sbs)
  • Re: HOW TO MAKE CONNECTION ON SQL SERVER USING MS ACCESS AS A PLATFORM
    ... Use MS Access ADP project. ... Use ODBC with *.mdb format, linking tables in SQL Server database. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Do I need to set..
    ... For ADP and MDB files, your Pen flash drive will work is there is already a ... that could be used to attache the database files. ... with an MDB database file. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Official Status of SQLServer 2005 ADP
    ... solution might be to use ADP. ... With MDB and Linked tables, the only ways of accelerating things are the use ... of Views and the cumbersome use of SQL passthrough queries. ... > SQL Server, and carry on using Access like I aways had. ...
    (microsoft.public.access.adp.sqlserver)