Prev: make an activex control safeforscripting and SafeForInitializing
Next: Querying userdomain for currently logged in user
From: Marvin van Dongen on 11 Jun 2005 03:15

"Ken Halter" <Ken_Halter(a)Use_Sparingly_Hotmail.com> schreef in bericht
news:esQRy6fbFHA.348(a)TK2MSFTNGP14.phx.gbl...
> "Marvin van Dongen" <marvinNOvdongenSPAM(a)hotmail.com> wrote in message
> news:42a9ba52$0$57958$dbd4b001(a)news.wanadoo.nl...
>>
>> After some more investigating, i found out that when i load each form
>> individually, it creates errors for any control that is loaded. What can
>> it be????????
>
> If you try opening a form that contains ActiveX controls, without opening
> the VBP file first, the references in the frm file will be considered
> invalid (a VB quirk). If you open a new, blank project, select Add Form
> and browse to a form that contains ActiveX controls, the controls will be
> added to the toolbox automatically. A bit strange <g>... anyway, opening a
> FRM file without loading a VBP file first doesn't work well if any ActiveX
> controls are on the form.
>
> --
> Ken Halter - MS-MVP-VB - http://www.vbsight.com
> DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
> Please keep all discussions in the groups..
>

Ok, but when i open that frmMain in VB, i get:

Automation error 440
Device I/O error
Automation Error

It is however possible to view the code. I just can't get the form view.

Marvin


First  |  Prev  | 
Pages: 1 2
Prev: make an activex control safeforscripting and SafeForInitializing
Next: Querying userdomain for currently logged in user