Hi Kevin,

I sometimes get that error too with NFL. The error is caused by a
mismatched variable and value. I.E. If you have an integer type
variable and pass it a floting point value like 1.5 VB 6 will display
that error. However, as I know Jim Kitchen doesn't use explicit type
coding, has Option Explicit off, the VB Runtime should do the type
conversions automatically, but doesn't appear to in this case. In
short it is a bug in the game, and only happens once and a while at
least for me.

Anyway, this kind of runtime error is hard to track down if you are
not type coding your code, and why not using explicit datatyping is
bad. were the program properly datatyped with Option Explicit enabled
the compiler would have flagged this error when compiling, or at least
it should since it would send up a read flag.

HTH

On 4/16/11, kevin lyon <[email protected]> wrote:
> Hi, just tried to play this on my laptop running windows 7. It all seems
> fine until the game kicks off, I then get an error saying:
> Runtime 13
> Type mismatch ... ok button
> And the game closes.
>
> Any clues anyone?
>
> kevin
> [email protected]
>
>
>
> ---
> Gamers mailing list __ [email protected]
> If you want to leave the list, send E-mail to
> [email protected].
> You can make changes or update your subscription via the web, at
> http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
> All messages are archived and can be searched and read at
> http://www.mail-archive.com/[email protected].
> If you have any questions or concerns regarding the management of the list,
> please send E-mail to [email protected].
>

---
Gamers mailing list __ [email protected]
If you want to leave the list, send E-mail to [email protected].
You can make changes or update your subscription via the web, at
http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/[email protected].
If you have any questions or concerns regarding the management of the list,
please send E-mail to [email protected].

Reply via email to