Re: access 2007 really slow

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

We are using dbo, not mixed. I made sure the startup form and the form that
I am dealing with in this application has the record source qualifier to be
dbo
I also made sure all references to the tables have a prefix of dbo (w/i the
VBA code that was written, there were only a few select statements) No views
on this form, but there is one stored procedure and I was not sure how to
specifiy dbo for it. Below is what I have.

' set CommandText to Stored procedure name
objCmd.CommandText = "StoredProcedureName"
objCmd.CommandType = adCmdStoredProc

' Connect to the data source
Set objConn = CurrentProject.Connection
objCmd.ActiveConnection = objConn

' set stroed procedurer parmaters
objCmd.Parameters("@SID") = pubSID
objCmd.Parameters("@MemID") = pubMemID
objCmd.Parameters("@FirstName") =
Form_subfrm_DealerDealerPersons.TxtFirstName.Value
objCmd.Parameters("@LastName") =
Form_subfrm_DealerDealerPersons.TxtLastName.Value
objCmd.Execute

I also ran SQL Server Profileer while I did the test as administrator and
again as the end user. I did not really notice anything different between
the two traces.

Thank you for the suggestions... I am afraid that we may have to install
access 2003 for the end users until this issue gets resolved....

Toni


"Sylvain Lafontaine" wrote:

Hum, the fact that you don't have any problem while logged as an
administrator make me unsure that your situation is related to the ADP 2007
current problem of excessive number of requests about the structure of the
database made by ADP 2007.

You should take a look with the SQL-Server Profiler to see what's really
going on with your ADP.

Are you using a mix of owners (dbo + some other users) or if all the objects
belongs to dbo and also, in the second case, did you took the precaution of
specifying dbo. for all references to views, tables and SP in your queries
and SP? Finally, did you also took the precaution of setting dbo as the
Record Source Qualifier under the Data tabl of all your forms and reports?

--
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:7142A28E-1CA7-4997-B5AC-3706D15AAFBD@xxxxxxxxxxxxxxxx

Yes I also have read several complaints about the slowness of .adp What
puzzles me is why I do not experience this problem while logged on as
administrator.

After I posted this question we installed SP2 (12.06423.1000 SP2 - MSO
12.0.6425.1000) on one of our machines and I ran the same tests - log on
as
end user problem (slow connecting slow when typing in data), log on as
administrator - ok. The access application is connected to is fairly
small
DB, just over 1 gigabyte.
The form that I am testing has a sub form that prompt for first name and
last name only. When I type in 3 records -Test One, Test Two, Test
three,
it can not keep up (I am not a fast typist). The tables that this form
is
dealing with has around 2850 records. Let me know if you need additional
information.

"Sylvain Lafontaine" wrote:

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

  • Re: access 2007 really slow
    ... administrator make me unsure that your situation is related to the ADP 2007 ... database made by ADP 2007. ... Are you using a mix of owners (dbo + some other users) or if all the objects ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: access 2007 really slow
    ... use StoredProcedureName as the Record Source of the ... The old problem with ADP 2007 is not on how it executes each Record Source ... Sorry about the vagueness comment about the SQL Profiler (again new to SQL ... I also ran SQL Server Profileer while I did the test as administrator ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Display values on input form before save the record
    ... A possibility would be to rework your form so that the record source of the ... even with the procedure to create the invoice number I still ... One client enters in the store and asks for a product. ... tblB.B3, dbo. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: ADP - record source doesnt exist
    ... Try removing dbo from the Record Source and put it as the Record Source ... Are you using a Windows account or a SQL-Server ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Set column level permissions in Access adp
    ... you are logging into the database as a dbo ... For the adp, QA, and in EM, I ... >>itself and then denying update permission on the column ...
    (microsoft.public.sqlserver.security)