MERGING multi-page controls at runtime?

  • Thread starter Thread starter Patrick Pirtle
  • Start date Start date
P

Patrick Pirtle

Not sure if this is the correct forum to post this to, so I
would welcome suggestions of more appropriate lists.

I'm using VBA to program an application for use in
a software CADD package called "MicroStation."
The top-most control is a multi-page control with
15 pages. Two different groups in our office will be
using this application. However, one group will be
using pages 1-3 and 4-8, while the other group will
be using pages 1-3 and 9-15. I combined what
*could* be two applications because I didn't want
to have to make future changes to pages 1-3 in
two different apps. At runtime, the app determines
which group is using it, and only displays those
pages that that group needs.

Here's my problem--
I must have hit the limit of controls, because when I
add one more text label, I get an "Out of Memory"
error when I run it. Is there any way to split this up
into THREE applications--one with pages 1-3, one
with pages 4-8, and one with pages 9-15. Then,
at runtime, could two of these be "merged" into a
single app with a single (visually) multi-page control?

TIA for any help and suggestions.
 
I would suggest that you write a single ActiveX control in Visual Basic 6.0
(NOT VBA)
This control can have any number of controls on it and you can fully test
and develop it in VB.

Once complete you can then simply place your single ocx on to the Outlook
form.
 
Michael -

Many thanks for your response! As I know nothing about
ActiveX controls, I've been looking them up online. If I
understand you correctly, you're saying that using VB will
get around the (apparent) memory limitations of VBA,
while still letting me use the VB-based control in a VBA
form?




Michael said:
I would suggest that you write a single ActiveX control in Visual
Basic 6.0 (NOT VBA)
Click to expand...
[snip]
 
Yes, but it takes a little understanding.

--
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


Patrick Pirtle said:
Michael -

Many thanks for your response! As I know nothing about
ActiveX controls, I've been looking them up online. If I
understand you correctly, you're saying that using VB will
get around the (apparent) memory limitations of VBA,
while still letting me use the VB-based control in a VBA
form?




Michael said:
I would suggest that you write a single ActiveX control in Visual
Basic 6.0 (NOT VBA)
Click to expand...
[snip]
Click to expand...
 
That's good, because all I've got is a *little* understanding.
Hehe

Michael said:
Yes, but it takes a little understanding.


Patrick Pirtle said:
Michael -

Many thanks for your response! As I know nothing about
ActiveX controls, I've been looking them up online. If I
understand you correctly, you're saying that using VB will
get around the (apparent) memory limitations of VBA,
while still letting me use the VB-based control in a VBA
form?




Michael said:
I would suggest that you write a single ActiveX control in Visual
Basic 6.0 (NOT VBA)
Click to expand...
[snip]
Click to expand...
Click to expand...
 
Back
Top