deluxeinformation@gmail.com wrote:[color=blue][color=green]
> > It does sound workstation related but still a security issue. What are
> > the sql privs the workstations have. Are the workstations identical.
> > It sounds like its the workstation privs not the user privs.
> > However....
> >
> > Do you have both sql and access security involved? If so, it could be
> > the access sequrity file that is stoping it on the workstation not the
> > sql security at all. This sequrity in access is held in the
> > system.mdw. Try creating a new system.mdw via workgroup administrator
> > under tools security. This will disconnect the existing security and
> > create a new empty access security on the workstation.[/color]
>
> Correct me if I'm wrong, but I don't think Access workgroup security
> applies when the application is an ADP. And I'm not sure how one
> defines security at the workstation level for SQL server. I'm not
> saying you're wrong, I just am not aware of SQL being aware of specific
> workstations, only roles and users.
>
> I would first make sure that each user is utilizing an identical copy
> of the ADP or ADE by copying a version from a machine that does work to
> one that doesn't, and make sure that both users' accounts on each
> workstation reference the same copy.
>
> Bruce[/color]
You're correct - MS-Access workgroup security is not available in ADP
files so I don't think that's an issue. I've not heard of workstation
security but so I'm "guessing" that's not it either.
Here's what I did find though:
The following workstations do not prohibit changing data and have the
following versions of ADO:
Workstation A: 2.81.1117.0
Workstation B: 2.71.9030.0
Workstation C: 2.71.9030.0
The following workstations do not allow the user to change data with
the exact same application, having the exact same user as the
successful user on A,B and C:
Workstation D: 2.53.6200.0
Workstation E: 2.53.6200.0
Now this is kind of an odd error to blame on a version of ADO but
sometimes when you line up the right variables and toss in an odd
version DLL you get spastic results. I'll post the results of my test
after upgrading D or E with the latest MDAC. I have to go through the
red tape of getting corporate support team to do it though - won't let
me do it.
Thanks for the feedback everybody