re: Error number 16 - Expression too complex

Tony — Sat, 23 Feb 2008 08:38:31 GMT

Tom, Bad DLL Calling Convention is already mentioned on the decompile page.

re: Error number 16 - Expression too complex

Tom Wickerath — Sat, 23 Feb 2008 08:18:45 GMT

Hi Tony,

Funny you should mention this. Just last week I experienced a similar (possibly the same?) error number. I was getting a very strange error as soon as I hit the End Sub statement in a combo box AfterUpdate procedure that called a function in a stand-alone module:

Private Sub Country_NotInList(NewData As String, Response As Integer)

Response = Append2Table(Me.Country, NewData)

End Sub

The function being called was Allen Browne's code to add a new value to a lookup table, when a user types it into a combo box. The function was working fine. In break mode, one could see that the error was raised as soon as the End Sub line shown above was run. The new data was added to the table correctly. One of the first things I tried was a decompile, which fixed the problem, so I was no longer able to document the exact error number.

Also related is this tip from FMS, where they talk about Error 49 getting fixed with a decompile:

www.fmsinc.com/.../Bad_DLL_Calling_Convention.asp

Tom