Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems progammatically Updating some AP Optional Tables

Status
Not open for further replies.

ryslepel

Programmer
Jun 8, 2007
14
ZA
I have created a user with "SUPER" AP rights in fact the user has Full rights too Adminstrative Services and Common Services.

When i use view tester on APOBLO,APPJDO,APPJHO,APOBLJO it shows that the user has only got inquiry rights, but for APIBDO,APIBHO,APRPDO,APRPHO,APTCRO,APVENO,APVGRO,...
The User has Full Rights: Add,Modify,Delete,Inquiry,Post

Why is this so?[ponder]

Accpac 5.3A
 
Rights are assigned by function, not by view.
Did you give the user posting rights in AP?
 
The User has full rights to AP
Everything, including Transaction Optional Fields has been granted.

Using my little app the user is able to post to certain AP tables but not to APOBLO which i need the user to do.
 
When a invoice has been reconciled my app inserts puts a record into the APOBL table that acts like a flag...well it is flag.

Offcourse with admin this works perfectly.

I've decided to create my own view but i still would like to know why a user with all the rights to AP only has inquire rights to:
APOBLO
APPJDO Posting journal Detail Optional
APPJHO Posting Journal Entry Optional Fields
APOBLJO Job Detail Optional Fields

But has the full spectrum of rights to all the other Views, including some of the other option views/tables.

Am i just being stupid or is there a solution for this?
 
OK, so you are updating AP invoices AFTER they have been posted, that makes a big difference.
Q: why are you adding a record to APOBL?

Why the user has view only rights to the other tables (after the invoice has been posted)? - because that is the way it works. The records have been posted to the tables, there is no need for write access after that point - normally.

You can change the view access by using
view.SystemAccess = VIEW_SYSACCS_POSTING
 
OH NO i meant APOBLO
I'm inserting records into APOBLO table not APOBL

I tried doing this
"view.SystemAccess = VIEW_SYSACCS_POSTING"
It didn't work!

you made happy their for a second...just a second though :)

 
Define "didn't work"... that's the most broad statement you can make.
What error message is reported when you try to insert a record into APOBLO?
 
Does your routine work with security disabled, or logged in as ADMIN?
 
My routine only works when i'm logged in as ADMIN

but i get "Description: Open Document Optional Field Attempt to perform Insert without security authorization."
When not logged in as ADMIN
 
view.SystemAccess = VIEW_SYSACCS_POSTING
has worked for me in cases where I needed to edit existing records in APOBL, I have never needed to insert any records though.
Maybe it cannot be done, in which case your alternate is to use ADO to insert a record into the table.
 
I have decide to create my own view to get around APOBLO's problem.

Busy implementing the changes.

Thanks alot for the changes.
 
I have decide to create my own view to get around APOBLO's problem.

Busy implementing the changes.

Thanks alot for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top