DB process not using table inquiry

[nspader]

I have used the knowledge of this forum to get me through some steps in this DB up til now, I am hoping you all can help me get through the next step.

I am creating a work schedule based upon different criteria. Since the code for this is very long I am going to post the DB along with this post.

The problem I am having now is that when it creates the schedule I need to have it use existing tables to see if there are shift requests and days off, etc.

It is clear that when the code runs it does not properly vies the recordset information. I believe that if we correct the first clear problem I can use it to correct the rest.

In the DB the code runs under the form - frmShiftConfiguration. I have it set up to vies tblHoliday and if the vDate is the same as a date entered intot he table it should move to the next vDate and not enter any information into the tblShift Detail.

I have left in a May schedule to show results. If you check code by running a schedule...Please use qryClear to clear results and run May as that is the only month with a holiday scheduled. (In Calendar view it shows holiday correctly because on my code for modCalendar, But if you view table 5/26 was still scheduled)

Please take a look at it and let me know if you can figure any of this out. Thank you in advance for your help. I apologize if this isnt clear. Any questions please ask.

Nick

P.S. I am using Win2000 and Access2000 for this DB.

[nico5038]

It's very hard to understand what your code should achieve.
So I'll concentrate on giving advice to find out where it goes wrong.
Just place a breakpoint (click in the left ruler of the code) on the first statement of the code behind the button you use to trigger the shift processing.
Now open the form and press the button.
The code will stop on the breakpoint and you can use F8 to single step through the lines. Holding the mouse pointer above a field will show the contents and when a query string is build you can use in the immediate window a ? as print statement to see the query like:
?strSQL
This query can be pasted in a new query's SQL text and thus tested for the expected rows.

Hope this give you a way to solve your problem.

Nic;o)

[nspader]

Thank you for you advice.

I was able to work my through it after seeing a few different posts on the web.

Nick