Search results

I thought about that, as this was written as a sub only because I don't need a return. No, I didn't test it. I did run one more test, on the dummy code. took the 64 bit box, unplugged it, put a 32 bit box identically configured (best we can, anyway) and ran it. So, runs fine on (XP) Access...

Yes, took out everything except the call. It is the call itself that is failing. Even removing the variable doesn't make it work. Did not attempt to decompile. Didn't think about that. Also would be better if the code were created on a 64 bit machine, but I don't have that available...

Still no joy in Mudville. Variable is clearly defined as Integer in main, and as required integer in sub variable list. Should be no problem. Still get error -- before anything else happens -- in the subroutine (ie, no line of sub runs.) Changed name of subroutine using Find - Replace...

Re: gutting procedure. In fact, I've taken all the other lines from everything else, at this point, and left only a bare skeleton to initiate the call with a couple message boxes to define location. Haven't tested it, machine is in use for other items. Will drop feedback here after I test. - J

OK thanks. Let me see if I understand what you've said here. .... calling routine Dim iSomeInt as Integer '<-- this defines the variable in the calling environment? ' and is missing (variant) call sbWaitaSec(iSomeInt) ..... Dim Public...

Because I was receiving the error, I added a first line to the sub, a debug line -- in this case, a msgbox. It never prints the message. Best I can tell, it is the call itself. Thanks. - JP

Hello from a nubie, I have a piece of code, written in 1996 and modified slightly through the years. Sub Main() ' in form #1, mouseclick on button brings up form #2, Dim btest as Boolean btest = CheckWinWedge End Sub ' To be clear, I've removed all the other code, leaving...