Access ADP newbee

[bradmaunsell]

I just ran my first Access MDB to ADP

Frontend is on my development laptop.
MDBE 2005 Express is on my laptop and SQL 2005 workgroup was just installed on our server.

Application for first convert is very simple Access 2003 application having just 4 tables, 2 forms and 2 queries.

Everything converted OK.

Here is my question, I looks like the forms are still bound. Do the forms have to be "manually" re-coded for unbound form operation?

I do understand how unbound form process is open form, connect to database, get data, populate text boxes and disconnect from database. And then, the finial updates opens again, updates the tables and closes.

But, a second question is, how do you create an UNBOUND form having multiple records? For example, an invoice data entry form having a single record header and a separte detail section having multiple records. I know how to do this with BOUND forms.

Thanks,
Brad
Burlington, Vermont

 

[bradmaunsell]

Let me add one more question to the previous submit.

Does an ADP project form, that is bound, have any PERFORMANCE advenatage over a regular Access application that uses an ODBC connection to the SQL database?

I know the ADP uses the SQL engine and the Access with ODBC uses the Jet. I'm just not sure I know anything about the preformance differences.

Thanks again.
Brad

 

[belovedcej]

For the first question - I don't know - I avoid continuous forms except in a read-only bound form.

For the second -

In my experience, the ODBC way makes queries and reports run more slowly.

But I don't have much experience with ODBC beyond that - I can tell you I like ADP because it is "cleaner." There are no queries on the Access side so it is a more true back-end/front-end. And I didn't have to learn how to write pass-through queries. Instead I just write views and stored procedures on the server. It seems to me that the more "layors" that are gone through, the more likelihood problems could develop. And one other thing to consider - what if some day this app grows and needs to be upgraded to .NET or something? It makes sense to do just about everything via sotred procedures so the development of a new front end won't be as cumbersome.

 

[cmmrfrds]

Why do you want to unbind the Form?

The ADP connection to SQL Server is client/server, where the query processing is done on the server.

The ODBC connection must bring the data back to the Client to execute the query. So, the bigger the tables the more advantage using the Access ADP.

 

[bradmaunsell]

Perhaps your response is the answer I have been seeking.

My concern is performance.

We are current using MDB tables linked to Access 2003 front end. We have only ten users but the performance is very slow.

I know the MDB maitains an open connect from the bound form to the database (of all records).

I was not clear on how an SQL database bound to a form have multiples records worked. As you mentioned, because everything is done on the server, the bound / not bound becomes something of a moot issue.

I was thinking it was neccessary to connect, populate the multiple record form (like an invoice) and then disconnect from the database. Then before existing the form, connect, validate and update and finally disconnect again.

Thanks for repsonse.