If you've read previous blog entries here you'll know I've had problems with ranges. I'm sticking with the "range where" construct for the foreseeable future because.
I have a window that the user provided an ID field (a string) to adjust some cost data. When they provided the ID and processed their first result I clear the window then they would enter the next ID. Dex promptly kicked an error 18 - Missing.
Turns out what was missing was not the data, but a "first" in my "get" clause. Because the range included multiple results "get" cannot be used on its own. Once I provided "first" all was well.
No comments:
Post a Comment