Discussion:
Unable to create component
(too old to reply)
John G
2008-12-09 01:49:51 UTC
Permalink
I have a form (A) which, when run stand alone, works fine. I have a second form (B) which, when run stand alone, also works fine.

However, when I run form A, close it, and call form B, I get the error "Unable to create the component."

It stands to reason something I use in form A conflicts with something in form B (I cannot even open the form). However, I could not find anything after a search of the knowledge base or the web.

Can anyone help with this?

Thanks
John G
2008-12-09 02:11:11 UTC
Permalink
I should have provided details: WinXP SP2 up to date; dBASE Plus 2.6.01 build 1905x. I have lots of memory and disk, this problem form is almost the only application running.

John
Post by John G
I have a form (A) which, when run stand alone, works fine. I have a second form (B) which, when run stand alone, also works fine.
However, when I run form A, close it, and call form B, I get the error "Unable to create the component."
It stands to reason something I use in form A conflicts with something in form B (I cannot even open the form). However, I could not find anything after a search of the knowledge base or the web.
Can anyone help with this?
Thanks
Bruce Beacham
2008-12-09 09:16:26 UTC
Permalink
Post by John G
I have a form (A) which, when run stand alone, works fine. I have a
second form (B) which, when run stand alone, also works fine.
However, when I run form A, close it, and call form B, I get the
error "Unable to create the component."
I've seen this but I can't pin down when.

IDE or runtime?

What happens if you run form B first, close it (but keep the reference
to the form in scope), run form A, close it, then re-open form B?

Or, what happens if you run form B first, close it, run form A, close
it, then run a second instance of form B?


Bruce Beacham
Ken Mayer [dBVIPS]
2008-12-09 04:35:51 UTC
Permalink
Post by John G
I have a form (A) which, when run stand alone, works fine. I have a second form (B) which, when run stand alone, also works fine.
However, when I run form A, close it, and call form B, I get the error "Unable to create the component."
It stands to reason something I use in form A conflicts with something in form B (I cannot even open the form). However, I could not find anything after a search of the knowledge base or the web.
Can anyone help with this?
It could be a variety of issues, the difficulty is knowing exactly what
your code is doing ... which of course makes it hard to diagnose without
more details. <g>

This particular issue usually means that too much system memory used for
resources is being used. When form A closes, try releasing the queries
and the form itself. See if that solves things.

Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase
John G
2008-12-09 21:45:04 UTC
Permalink
Thanks to all who responded. I solved the problem and in case my experience will help someone else, here is what I found.

These forms (A/B) are simple forms with minimal controls and provide a front end for data maintenance. The comments I found about the error focused on memory issues, leaks, GDI, etc. I did find one thread discussing a bug in query and using EXACT. However, none of these worked for me.

What I found was both forms were connected to the same table, but in different ways. I had also modified the table, adding a new field and populating that field. I created form A, created form B, then modified the table. Form B worked fine but then the error appeared when I tried to access form A.

I corrected the error by matching the code in form A to the code in form B, in other words making sure each form was connected to the table in exactly the same way. Once that was done, the error disappeared.

I'm not a guru, so you may spot something in my explanation that says "Of course!" The challenge for me was the error message was so cryptic I had little information with which to troubleshoot.

So thanks for the assistance and perhaps this will help someone else.

John
Post by Ken Mayer [dBVIPS]
Post by John G
I have a form (A) which, when run stand alone, works fine. I have a second form (B) which, when run stand alone, also works fine.
However, when I run form A, close it, and call form B, I get the error "Unable to create the component."
It stands to reason something I use in form A conflicts with something in form B (I cannot even open the form). However, I could not find anything after a search of the knowledge base or the web.
Can anyone help with this?
It could be a variety of issues, the difficulty is knowing exactly what
your code is doing ... which of course makes it hard to diagnose without
more details. <g>
This particular issue usually means that too much system memory used for
resources is being used. When form A closes, try releasing the queries
and the form itself. See if that solves things.
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase
Ken Mayer [dBVIPS]
2008-12-09 23:01:14 UTC
Permalink
Post by John G
Thanks to all who responded. I solved the problem and in case my experience will help someone else, here is what I found.
These forms (A/B) are simple forms with minimal controls and provide a front end for data maintenance. The comments I found about the error focused on memory issues, leaks, GDI, etc. I did find one thread discussing a bug in query and using EXACT. However, none of these worked for me.
What I found was both forms were connected to the same table, but in different ways. I had also modified the table, adding a new field and populating that field. I created form A, created form B, then modified the table. Form B worked fine but then the error appeared when I tried to access form A.
I corrected the error by matching the code in form A to the code in form B, in other words making sure each form was connected to the table in exactly the same way. Once that was done, the error disappeared.
I'm not a guru, so you may spot something in my explanation that says "Of course!" The challenge for me was the error message was so cryptic I had little information with which to troubleshoot.
So thanks for the assistance and perhaps this will help someone else.
Glad you figured it out. Some of the errors are a bit cryptic.

Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase
Jan Hoelterling
2008-12-09 14:16:44 UTC
Permalink
Hi John,

do you know which component the error occurs on? I've run into this with
subforms when I have an overwritten open method in the form. Also, I've seen
it in connection with Treeviews (specifically, when dynamically creating
treeitems).

Jan
Loading...