I imported a number of Access 2003 MDBs and ADPs when we upgraded to Office
2007, and I never stop running into problems with the new version. The latest
one is that I find I can't edit fields in a SQL-Server (2005) table using an
ADP front end.  This worked fine before the ...

The user has moved from office 2003 to office 2007. The access adp solution
is developed in access 2003 and works perfectly in with office 2007 except
for some details.
How can I export more than 65536 records from access adp client to excel 2007?

I am exploring ADP, please bare with me if my questions appear to be too
simple or off-line.
I have converted my Access03 to an ADP project and another similar copy to
SQL tables only (just to see the different).

Is is better to open one ADO Connection to the database and persist it across
all forms or is it better to open the connection, execute the view or stored
procedure, and then close it?
Also, if I do keep the connection open can I open it in the login form and

I have a query in which I have several Alias Columns I must use in other
columns. However, every time I attempt to refer to an Alias the sql errs the
procedure.  Any suggestions, I have a very complicated Leave Query that needs
to determine leave updates for each month and refers ...