B
Baffled
Guest
Hi guys,
I have a secured database in Windows 2000, I have created a form that sets a querydef based on user criteria and produces a graph of the data. If I run it with Admin rights everything is fine, but if I run it with one of my users id's I get an error and the code stops. The users do have permissions to create new queries.
The error is a security issue referring to no permission to use 'MSysTables' object. I have set the options so all system/hidden files are displayed. I don’t have a table named 'MSysTables' – and therefore cannot administer rights for it...Am I missing something obvious? The back up does not produce this error where it resides, when coping it to a different directory all of the object security is reset, and the users have all rights to all objects. So I re-established the security for all objects and it produces the error again. I've created a new database and imported all of the objects (from current db and from backup) into it, that didn’t work for the front end or the back end. I even created a new workgroup info. file and imported everything again into a new database and I still get the error. Also tried jetcomp.exe. I’ve looked high and low for a solution on the internet, but I have not been able to find a cause or a solution. The only thing that was suggested is that it has something to do with using querydef. If anyone can help it would be greatly appreciated!
Baffled
I have a secured database in Windows 2000, I have created a form that sets a querydef based on user criteria and produces a graph of the data. If I run it with Admin rights everything is fine, but if I run it with one of my users id's I get an error and the code stops. The users do have permissions to create new queries.
The error is a security issue referring to no permission to use 'MSysTables' object. I have set the options so all system/hidden files are displayed. I don’t have a table named 'MSysTables' – and therefore cannot administer rights for it...Am I missing something obvious? The back up does not produce this error where it resides, when coping it to a different directory all of the object security is reset, and the users have all rights to all objects. So I re-established the security for all objects and it produces the error again. I've created a new database and imported all of the objects (from current db and from backup) into it, that didn’t work for the front end or the back end. I even created a new workgroup info. file and imported everything again into a new database and I still get the error. Also tried jetcomp.exe. I’ve looked high and low for a solution on the internet, but I have not been able to find a cause or a solution. The only thing that was suggested is that it has something to do with using querydef. If anyone can help it would be greatly appreciated!
Baffled