why would a 64bit windows still trip over this code(when all the code that wasn't compliant has been removed?)

[kbishop94]

Its really frustrating.

I originally had 'DTPicker' in my workbook that is used to enter and track incidents for my company. But, there are a handful of machines that are 64bit, and I couldnt find any compliant date picker modules that would work... so I finally gave up and just have a simple textbox for entering the date. (so i just went back to the way it was before when it worked before I started using DTPicker (wouldnt work with 64bit), and then later when I tried using some date picker modules/code (which was supposed to be 64bit compliant but I never could get any of them to work) that is floating around on the internet... well wouldnt you know it... the same 64bit machines that had a problem with the code before STILL has a problem with it now too even after I remove the offending code. What I am missing??

After I open a userform and then click on my commandbutton to copy the data to the worksheet it gives me this error ("TRIM" function):

Then, after removing THAT offending code (note where I changed the previously 'bad' trim code to green) it just moves down to the very next piece of code and says it doesnt like that one now... and then I can do the same thing to it, and then it just moves down to the next line of code, and so on...

What gives? Is my workbook possessed by satan? Because before adding any of the DTPicker stuff this same code ran just fine. Now it doesn't.

Please and Thank you for any help so I can fix this devilish code once and for all.

 

[mrshl9898]

Try replacing Trim with Strings.Trim

 

[Norie]

Have a look under Tools>Reference...

If there is anything marked as MISSING note its name and uncheck it, close and save the workbook, re-open and try again.

 

[kbishop94]

Try replacing Trim with Strings.Trim

Have a look under Tools>Reference...

If there is anything marked as MISSING note its name and uncheck it, close and save the workbook, re-open and try again.

Thank you. Both suggestions worked

ultimately though unchecking the reference box was obviously the better solution as there were still TONS of commands in the code that would of continued to trip it up without adding the " Strings. " to all of them...

Also... I CANNOT BELIEVE I never thought of checking for missing references... Its not like I didnt know about that... I have to do it ALL THE TIME whenever I send myself something from work thats in excel and I try to open it at home. I have to do that all the freaking time, yet I never thought of doing it here(!) Oh boy... thank god its friday y'all.