Re: Stored Procedure Disappearing

Make sure that the "Record Source Qualifier" is set to dbo; especially if
you didn't specify in the RowSource property.

How is the RowSource exactly written in your case?

Also, maybe you have simply a permission problem: the user doesn't have the
permission to run this SP under her account on the SQL-Server.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Barb" <Barb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FB78AAED-C81C-48B4-BCC8-60EF842885F0@xxxxxxxxxxxxxxxx
The owner of the sp and all of its component functions is dbo. I didn't
write it; it's something I inherited and must maintain. I should mention
that I am working with Access 2003. Anything else I ought to be checking?

"Sylvain Lafontaine" wrote:

Maybe a problem with the schema (also known as the owner) of the stored
procedure. Did you use dbo. when creating this SP and set the Record
Source
Qualifier to dbo or if you have used something else for the schema
(owner)
of the SP?

Also, the newsgroup for ADP is m.p.access.adp.sqlserver .

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Barb" <Barb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:447479EE-3612-4BF4-BD9F-84EEFA244BFC@xxxxxxxxxxxxxxxx
I have an Access application that produces various reports. One of them
is
a
summary report which obtains data from a large stored procedure
containing
many functions. When I pass the .adp/.ade file to a user, this one
stored
procedure disappears and the user is unable to run the report; however,
I
can
run it from my machine or from hers when I remote in. Do I need to cut
this
stored procedure up into several smaller ones, or is there a better way
to
get the application to the user?

Thanks in advance.





.

Relevant Pages

  • Re: ADP: Cant use stored procedure on remote SQL server
    ... Sylvain Lafontaine, ing. ... else then dbo as the owner of everything. ... If you don't mention the owner when creating a new stored procedure, ... Check also the owner of the SPInc stored procedure. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Setting control value based on a SQL Select statement
    ... @CRRNumber int OUTPUT, ... Sylvain Lafontaine, ing. ... The actual code I use to call my stored procedure is as follows: ... ClientID and GUID number to the stored procedure. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: QBF in an Access Project using a between
    ... work properly event without the Between clause. ... Sylvain Lafontaine ... stored procedure and probably you have tried to use something like ... @StartDate without adding it as a new parameter. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Stored Procedure in SQL Server vs MSDE 2005 SQL Server
    ... Sylvain Lafontaine, ing. ... converted to MSDE 2005 SQL Server Express. ... The stored procedure in the SQL server is called BOM2ECO_Difference_Get. ...
    (microsoft.public.access.externaldata)
  • Re: xp_logevent and service broker queues
    ... With EXECUTE AS OWNER 'dbo', the database owner of your user database needs to be 'sa' in order for the security context to be 'sa' in master too. ... This queue receives all messages and starts the stored procedure sp_AsyncReceive which is owned by the dbo. ... Maybe somebody can give me a hint how to call 'sysadmin' functions under the dbo user or how to change permissions for calling these functions in a stored procedure which is started by a service broker queue. ...
    (microsoft.public.sqlserver.security)