0

This was a similar thread, but still no luck. What causes this error? “Runtime error 380: Invalid property value”

This program has been out for years running on XP ~ Win8

A recent installation on a Vista Home Premium laptop is producing this error.

Here is the last code before the error:

 On Local Error Resume Next

 fSetup.Show

 If Err.Number <> 0 Then MsgBox Err.Description, vbCritical

 On Local Error GoTo 0

It does not it to the if clause.

In the form load of the target form, it never makes it to the If clause

If bTestMode Then MsgBox "Setting me.tag", vbOKOnly
Me.Tag = "FormLoad"
If bTestMode Then MsgBox "Me.Tag Set", vbOKOnly    
If bTestMode Then MsgBox "Setting me.tag", vbOKOnly
Me.Tag = "FormLoad"
If bTestMode Then MsgBox "Me.Tag Set", vbOKOnly

Thank you in advance.

Community
  • 1
  • 1
Xardoz
  • 39
  • 2
  • 6
  • Looks like your problem is down inside of your form, fSetup. What code does that run when it is loading up? (Form_Load, Form_Activate, et al). – Lynn Crumbling Jan 17 '14 at 19:22
  • 1
    Does fSetup use adodb? If so, you might be being bitten by the [win7 sp1 ADO guid mess](http://blogs.msdn.com/b/psssql/archive/2011/10/03/yes-we-made-a-mistake-and-are-finally-going-to-fix-it.aspx) – Lynn Crumbling Jan 17 '14 at 19:24
  • It is only happening a a Windows Vista Laptop, Window 7 work perfectly The second batch of code is what fSetup Executes, never makes it there. – Xardoz Jan 17 '14 at 23:24
  • Do you have anything in the Form_Initialize() method in fSetup? That code executes before Form_Load when you use the .Show method on a form that hasn't been created yet. – JeffK Jan 20 '14 at 22:29

1 Answers1

0

Turn out System Locale was set to Korean, causing non-unicode VB6 to have trama

Xardoz
  • 39
  • 2
  • 6