Re: access 2007 really slow

Tech-Archive recommends: Fix windows errors by optimizing your registry

They have been many complaints in the past regarding the lack of speed of
ADP 2007 and I don't use it myself personally exactly because of that. Some
people have reported an improvement with SP1 but I never tested it
personally. It's interesting to see that you don't have any problem when
you are logged as an administrator. Could you give us some more details?

SP2 for Office 2007 is out, so you should give it a try:

http://support.microsoft.com/kb/953195

http://www.microsoft.com:80/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"Toni" <Toni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AF0CA67D-6E0B-4B34-8999-2E6B9DACEDA0@xxxxxxxxxxxxxxxx
We recently upgraded from access 2003 to access 2007 and SQL Server 2000
to
SQL Server 2008 Standard edition. We use ODBC to connect to the backend,
a
system DSN was created with a SQL Server driver.

I noticed our adp access apps are really slow, can not keep up with the
end
user typing a name into a text box. I have done the following tests on 2
different machines. One machine has access 2003 and the other mahcine has
access 2007. The machine with access 2003 is fine (I logged on and
tested
the application as the end user and as adminisstrator) The machine with
access 2007 I logged on as administrator and the application was fine, I
then
logged on as the end user and the application was real slow. I then
gave
the end user full control on the C: program files - Microsoft office
folder
to see if that would make a difference, that did not. Does anyone have
any
suggestions on what else I can try?

Thanks
Toni


.

Relevant Pages

  • Recordsource only available to Administrator on clients
    ... In my ongoing development of a SQL Server back-end / Access adp front- ... it runs fine on a given client if the client ... logon is either The Administrator, or if I change a test user's ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... I decided to go on with adp project, and i have created a store ... But queries are different stories. ... In SQL Server, there are Views, Stored Procedures, UDFs. ... Also, when you decide to use MDB front-end, you can choose use MDB ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • 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: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)