Display Error when Textbox is over a Certain amt

OK You might be on to something.

This error message tho, is for the searchable form, not the input form.

BUT, this hidden field that sums the total and checks would be great, but I don't know how I would add the date aspect into the calculation. Right now on the Search Form, it only returns dates that are 365 days previous to today's date. Then it sums the total.

I'm wondering if I should just allow Data Entry to the continious form so that a user can see the total at all times and I could set up the Error Message there if they exceed 20 K.

That was the VB Code that I encountered when I activated the VB Editor while looking at the "Before Update" Button of the Add Entry section.

I would imagine that the Hidden Field would rely on similar rules to those used in the Search Form. In fact I cannot completely understand why those rules are not available/required at all levels.

Sum(CommAmt) { Where [PO Date] is in the correct Date Range }
 
Ok, I think the easiest way to solve my entire problem would be to do this:

Instead of checking a value on the Input screen (which has given me a world of trouble because I have to factor in certain records by their Dates) TO INSTEAD, allow Additions on my Continious Search Form.

This way, the user will search a particular UNSPSC code, they will be able to obviously see if this code exists because they will see records under this given code and if the Search Form brings back no results, THEN the user goes to the input form. This way, this database will only use the "Input Form" on all new UNSPSC code entries. This way, I can set up code in the CommAmt field, like i do now, that will not allow this first single entry to exceed the limit.

Now the user at a later date comes to enter in the 2nd record under this given code. They can see the Amts of records within the current year and they can enter the next record.

I need help with two things still:

1. When I go to add a new record from this page, all the fields go blank including UNSPSC code. Is there any way for the user to not have to reenter in the same code, or in otherwords, when they go to create a new record, can it "Save" the former number so that the user will only have to enter the other fields such as PODate, PONumber, FedID and CommAmt. SOLVED!

2. To again safeguard entries that exceed the limit, now on the continious form, can I create a CommAmt check that will Sum up all the CommAmts for a given UNSPSC code and return an error/will not save the latest addition if the last value (and the sum of the former ones) exceeds the limit? Still in question...
 
Last edited:

Users who are viewing this thread

Back
Top Bottom