Hi,
We may need to double check the default mdw file on the clients; make sure
it uses admin account by default instead of other accounts. In other words,
on the client they did not change/customize any security account.
In addition, we can check if you take away permissions on the
MSysAccessObjects table in the database? If so, that can cause the issue;
Sincerely,
Alick Ye, MCSD
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "C" <(E-Mail Removed)>
| Sender: "C" <(E-Mail Removed)>
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.security:2129
| NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
| X-Tomcat-NG: microsoft.public.access.security
|
| Thanks again for the response. According to what I have
| read in the various tech blurbs, I should not need to (and
| should not) release the MDW file since the client's
| Default MDW file with the Admin user will have the rights
| that they need to use the application. I am still
| perplexed why this application works fine on non-XP
| machines and would welcome some information on why this is
| happening in XP environments.
| P.S. I was hoping that I would get an MS response within
| the advertised window of time for this managed newsgroup
| and would also like to know what I have done to not
| receive the response. Is this normal?
|
|