07-23-2002, 06:57 AM
I have a strange program in running a VB exe. I have two VB exes...both of these exes run successfully on one computer. On another computer, one of the exe will load and run correctly, but the other gives me a :
Run-Time error '3265' Item not found in the collection corresponding to the requested name or ordinal. This is not the common 430 error and I know I have the ODBC source on the workstation...any ideas of how to fix this error? thanks
07-23-2002, 07:34 AM
It should be easy to fix once you figure out what line of code is
raising the error. I would insert error handling code at any point
where collections are being accessed. Since you mention ODBC,
I assume this is a database app. One possible area is the actual
database table might be different on the two computers. If one
contained a field in a table that the other one didn't have, it would
raise this error with a statement like...
value = rs.Fields.Item("myfield").value
(or value = rs!myfield - same thing)
07-23-2002, 07:40 AM
This is my problem: I am running the exe on another computer, so I have no way of debugging the error at that computer. At the host computer, which has VB 6.0 the code works fine, so how can I find the error? Any ideas. The other computer does not have VB 6.0 and it is receiving the exe via the "P&D". How can I troubleshoot this error without knowing where the problem is?
07-23-2002, 07:55 AM
The best way is to include code that writes all error info to a log
file. The App.StartLogging and App.LogEvent methods are
provided for this. Sometimes, you have to include line numbers on
all suspect functions so that you can use the undocumented Erl()
statement to report the line number the error occurred on.
Putting line numbers on the code is easy with the MZ_Tools addin.
The link to get MZ_Tools is in the Handy Tools thread at the top
of Tutor's Corner. You should also look for my Debugging tutorial
there (posted by Billsoo) to help you (especially with using the
App.StartLogging and App.LogEvents methods).