• Problem in DBLookup when checking duplicate leave allowances

    By Ted Hardenburgh 2 decades ago

    I found a problem when trying to enter a leave allowance for another user. I was getting an error trying to navigate from the start date to the first leave field that said there was already an allowance for me for the year. There wasn't, and in looking at the code it did a DBLookup to the 6th column of the (All Leave Allowances) view, where it looks like it expected to find the Name+Year value. That value was stored in the 1st column, so I updated the value to check the new column and it's working now.



    Looks like a great app - I've got one group very excited about using it, after that, we'll hopefully move it out to more people!

    • The DBLookup Just Checks for the Existence of the Document

      By Bob Brodsky 2 decades ago

      Ted,



      Thanks for your interest in Vacation Request!



      In the DBLookup that you mentioned I only check for the existence of an Annual Leave Allocation document when a new one is created. Nothing is done with the value retrieved. So, the column retrieved is not relevent.



      The Name field on the Annual leave Allocation form defaults to the name of the person creating the document. The trick here is to be sure that the Name field has the name of the person for whom you are creating the Annual Leave Allocation before moving on to the Start Date or other fields.





      Hope this helps,

      Bob