Re: Error on insert: Invalid input parameter values...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

A second possibility would be a different "Default Schema" between the
default account used when the user is not part of the Sysadmin group and the
one used when it is. In SQL-2000, this default account is usually dbo. and
it has always be suggested that people using ADP keep using this default for
every account and that the Record Source Qualifier of every form be set to
dbo.

If you didn't follow the same rule with your project on SQL-Server 2005,
this could possibly be the source of your problem.

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


"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:ua$rP%239MJHA.5692@xxxxxxxxxxxxxxxxxxxxxxx
Well, this looks like some permission problem or a problem with the
default schema or a problem with the fact that Access 2003 doesn't really
support the advanced schema that you can have under SQL-Server 2005.
Using advanced schemas won't give you any problem when executing the query
under SSMS but it might well be another story when executing from ADO or
under ADP. If you have many tables with the same name but under different
schemas; this could be even worse.

What does this gives if you try to execute this query not from SSMS but
from ADP using an ADO connection such as CurrentProject.Connection?

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


"JoelB" <JoelB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EB33D75A-01D9-4125-BE04-8B569800BD28@xxxxxxxxxxxxxxxx
Is there nobody out there who can offer any insight on this matter?

"JoelB" wrote:

I have a form that works fine for updates and deletes, but when I try to
insert a new record as a non-sysadmin, I get this error:

Invalid input parameter values. Check the status values for
detail.

In Profiler, the last thing before the error is the sp_prepare statement
for
the insert.

I am familiar with the issue with identity columns (this table is using
one)
and views, however in this case the form is bound to a stored procedure,
and
the stored procedure (and resync) both tie directly to the table, not to
a
view.

The other interesting thing is that the insert works fine when I grant
the
user sysadmin server role. Using Profiler I captured the insert that
follows
the sp_prepare. I then removed the user from the sysadmin role, and ran
the
insert from SSMS as that user and it worked fine.

The user normally has access to the tables through datareader/datawriter
roles, and can insert data in other forms in that same ADP.

Can someone help?

TIA,
Joel

SQL 2005 (9.00.3073.00) and Access 2003 SP3.





.

Relevant Pages

  • Re: Trouble Extending Schema
    ... The SMS Server account has full control of the new system ... I've tried running the extend schema application from each of the domain ... Could you be more specific on how you are "manually" extending the AD ...
    (microsoft.public.sms.setup)
  • Re: ADAM Permission Questions (Hiding the Existence of Objects)
    ... Yeah he can try to ACL attribute definitions in the schema but who knows what that would break. ... will the inability of an account to see an attribute in the schema ... Is there a way to hide the existence of OUa and OUb from a specific account ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADAM Permission Questions (Hiding the Existence of Objects)
    ... Schema has Authenticated ... will the inability of an account to see an attribute in the ... Is there a way to hide the existence of OUa and OUb from a specific ...
    (microsoft.public.windows.server.active_directory)
  • Re: Child Domain
    ... users can log into OWA with the win.example.com account to access the ... The schemas of the two forests are completely separate. ... I wouldn't 'pound away' at the schema in win.example.com though as if you ... mailboxes in the same forest as the Exchange organisation. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Active Directory Schema
    ... "Herb Martin" wrote: ... account not all the fields are copied over to the new account. ... I have tried to edit the schema in Active Directory but with no luck; ...
    (microsoft.public.windows.server.active_directory)