The Setup:
I have a main form with a listbox to the left and a subform with a listbox on the right. As the user selects an item from the main listbox the listbox on the subform(to the right) should update to reflect such.
When the rowsource to the subform contains a query with:
I get the above error when it reaches the following line of code:
When I remove the 'right' function and the query is just matching the [NSN] field things are ok. But with the 'right' function present I get that error on all machines running WinXP Pro 2002 w/ SP1. No problems on WinXP Pro without the SP1 nor on Win 2k w/ SP2.
For the time being I have removed the 'right' function, but was wondering if there was something I could do to allow me to use the 'right' function and not get that error?
Thanks guys
P.S. The NSN field does contain "-" characters along with numbers, stored as text. I did some searching and found a similar error with that as a problem, but no fix to my specific issue.
All lessons learned from the School of Hard Knocks........at least tuition is cheap.
I have a main form with a listbox to the left and a subform with a listbox on the right. As the user selects an item from the main listbox the listbox on the subform(to the right) should update to reflect such.
When the rowsource to the subform contains a query with:
Code:
right([NSN], 11)
I get the above error when it reaches the following line of code:
Code:
Me![frmSUBAssignDocs].Form![List8].Requery
When I remove the 'right' function and the query is just matching the [NSN] field things are ok. But with the 'right' function present I get that error on all machines running WinXP Pro 2002 w/ SP1. No problems on WinXP Pro without the SP1 nor on Win 2k w/ SP2.
For the time being I have removed the 'right' function, but was wondering if there was something I could do to allow me to use the 'right' function and not get that error?
Thanks guys
P.S. The NSN field does contain "-" characters along with numbers, stored as text. I did some searching and found a similar error with that as a problem, but no fix to my specific issue.
All lessons learned from the School of Hard Knocks........at least tuition is cheap.