Kenny
Giving your invoice clerks way to much lattitude and not enough guidance.
Why not limit the entry data by using a user defined combo box so you
can control the
entry information.
Dick Fey
On 8/10/2012 12:50 PM, Kenny Camp wrote:
Requesting ideas, I'm stumped.
We are enhancing the integration RBase with our UPS and FedEx shipping
programs using Oterro. These shipping programs are looking up our invoices
for shipping information ad account numbers when the billing should go to
either the "Shipper" or "Receiver".
This computed column expression "(ifnull((IFEQ('Ft
Chgd',acctnumout,NULL,acctnumout)),'S','R'))" works great to update the
column with "S" or "R".
Then I use a view to display the text "Shipper" or "Receiver" which these
shipping systems read and bill accordingly.
When I first wrote this routine I had a simple rule, if the accountnumout is
null then bill the shipper (us) else bill the receiver with the valid
accountnumout value. This works for 95% of shipping.
Then we discovered the invoice clerks sometimes enter "Ft Chgd" so I wrote
the above expression.
After further discovery, they would like several (maybe a dozen) text
entries (not null) that would still resolve to "S" including "Prepaid", "Ft
Chgd", "Prepaid TX", "Our Expense", etc... that they are adding to a table.
I don't believe I can write a computed column expression that complicated,
and since they often edit this field after the invoice is complete, I like
the way the computed column works.
My experience with stored procedures and triggers is limited but I believe
that updating the same table with a triggered stored procedure would cause
problems (recursive).
Just for fun I was able to write a SP that works with an update statement,
but when editing with the Data Browser gives me the "another user has
changed the data" like I expected.
Any ideas of a better or different approach?
Thanks, Kenny
