Hello All

I'm going to use ActiveX Grids. I have next

1) Library MSDataGridLib
C:\WINNT\system32\MSDATGRD.OCX
Microsoft DataGrid Control 6.0 (SP4) (OLEDB)

2) Library MSFlexGridLib
C:\WINNT\system32\msflxgrd.ocx
Microsoft FlexGrid Control 6.0 (SP3)

3) Library MSHierarchicalFlexGridLib
C:\WINNT\system32\mshflxgd.ocx
Microsoft Hierarchical FlexGrid Control 6.0 (SP4) (OLEDB)


What is the most powerful ?
What from them the most like Access Datasheet

Thank You
illya

I would not use any of them, and would consider just using a regular form in
ms-access, but use the form in continues form mode.

Take a look at the following screen shots of how I make grids in ms-access.
You really do not need any extra controls. Besides, if you start using
ActiveX controls, then you need the developer edition of those controls, and
you also thus need a "installer" when you distribute your application.

In fact, you will find the continues forms in ms-access WAY BETTER then most
grid controls.

check out my screen shots of continus forms:
http://www.attcanada.net/~kallal.msn/Articles/Grid.htm

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
kallal@msn.com
http://www.attcanada.net/~kallal.msn

Thank You for Your reply.


But problem with Access SubForms in next:
==============================
Hello All

I have splitted my MDB into MDE and data MDB.
In old whole MDB I have next piece of code to
create an instance of a form with subform.

.....
Dim objForm As New Form_frmParentFormWithSubForm

objEditForms.Add objForm
With objForm
.FillValues
.Visible = True
End With
.....


When I save it as MDE this code opens only a parent form.
I have next ideas, Please comment


- It comes from that form in MDE is not visible outside
- it can be fixed, I need ....
- it can not be fixed

- I need use special naming with usign Namespaces like MDE module name

- I need create sub form by new as well and assign subform to
subform/subreport property
- it can not be done because subform/subreport property is readonly
- it can be done by "special" SysCmd or etc

- How DoCmd.OpenForm works ? Because without creating an instances I can
open
form with subform outside MDE
- I need to call DoCmd.OpenForm by special way
- It will not help

- I need to write C/C++ DLL to write special version of DoCmd.OpenForm

- I need use MS Forms

- I need to use third company's OCX

- Any other



Thank You
illya
===============================
"Albert D. Kallal" <kallal@msn.com> wrote in message
news:E7wgb.37047$pl3.16069@pd7tw3no...[color=blue]
> I would not use any of them, and would consider just using a regular form[/color]
in[color=blue]
> ms-access, but use the form in continues form mode.
>
> Take a look at the following screen shots of how I make grids in[/color]
ms-access.[color=blue]
> You really do not need any extra controls. Besides, if you start using
> ActiveX controls, then you need the developer edition of those controls,[/color]
and[color=blue]
> you also thus need a "installer" when you distribute your application.
>
> In fact, you will find the continues forms in ms-access WAY BETTER then[/color]
most[color=blue]
> grid controls.
>
> check out my screen shots of continus forms:
> http://www.attcanada.net/~kallal.msn/Articles/Grid.htm
>
> --
> Albert D. Kallal (MVP)
> Edmonton, Alberta Canada
> kallal@msn.com
> http://www.attcanada.net/~kallal.msn
>
>[/color]

"Illya Havsiyevych" <gavsi@ukr.net> wrote in message
news:blv2d2$1h2s$1@news.wnet.ua...[color=blue]
>
> ....
> Dim objForm As New Form_frmParentFormWithSubForm
>
> objEditForms.Add objForm
> With objForm
> .FillValues
> .Visible = True
> End With
> ....
>[/color]

I think the above should work just fine. Am I to assume that objEditForms is
a collection?

Also, .FillValues. Is that a custom method of the form (ie: a public
function?). How does that code work?

I don't see anything in the above that would case a mde not to work, and a
mdb to function. The only difference between a mde and mdb is that
un-trapped errors in a mdb re-set all your global vars. Perhaps you have a
un-trapped error in the mdb that resets your values (those values don't
re-set in a mde...but remain intact even AFTER un-trapped errors).

I would spend some time checking the above.

However, if you are really insisting on using a activeX control, then I
would suggest you ask your question for which activex control to use in a VB
group, and not a ms-access group, as most here don't use he activeX controls
due to the problems of references, and the need for a installer. I don't
know which activeX contorl is the best....but what is stopping you from
trying a few?

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
kallal@msn.com
http://www.attcanada.net/~kallal.msn

Thank You again

I'm not using ActiveX now.
objEditForms is a collection to store refs to all instances of created Forms
..FillValues is Form method but we can skip it. It is not important

If You are going to check smth do next:
1) create a form with a subform
2) create a code that can be visible outside mde that creates an instance of
this form
3) compile all above to mde
4) create other mdb, use this mde as reference
5) use code from mde to open an form

The main difference is next:
I'm not using DoCmd.OpenForm. In case of DoCmd.OpenForm all work
but I have only 1 instance. But I'm trying to have many

illya

"Albert D. Kallal" <kallal@msn.com> wrote in message
news:xaFgb.38800$9l5.1364@pd7tw2no...[color=blue]
> "Illya Havsiyevych" <gavsi@ukr.net> wrote in message
> news:blv2d2$1h2s$1@news.wnet.ua...[color=green]
> >
> > ....
> > Dim objForm As New Form_frmParentFormWithSubForm
> >
> > objEditForms.Add objForm
> > With objForm
> > .FillValues
> > .Visible = True
> > End With
> > ....
> >[/color]
>
> I think the above should work just fine. Am I to assume that objEditForms[/color]
is[color=blue]
> a collection?
>
> Also, .FillValues. Is that a custom method of the form (ie: a public
> function?). How does that code work?
>
> I don't see anything in the above that would case a mde not to work, and a
> mdb to function. The only difference between a mde and mdb is that
> un-trapped errors in a mdb re-set all your global vars. Perhaps you have a
> un-trapped error in the mdb that resets your values (those values don't
> re-set in a mde...but remain intact even AFTER un-trapped errors).
>
> I would spend some time checking the above.
>
> However, if you are really insisting on using a activeX control, then I
> would suggest you ask your question for which activex control to use in a[/color]
VB[color=blue]
> group, and not a ms-access group, as most here don't use he activeX[/color]
controls[color=blue]
> due to the problems of references, and the need for a installer. I don't
> know which activeX contorl is the best....but what is stopping you from
> trying a few?
>
> --
> Albert D. Kallal (MVP)
> Edmonton, Alberta Canada
> kallal@msn.com
> http://www.attcanada.net/~kallal.msn
>
>
>[/color]

I'm sorry very much,
Just subform work Ok
The subform with bound data table gives error

I created recordset by VBA and bound it at Form_Load time
and became Ok

Thank You again

"Illya Havsiyevych" <gavsi@ukr.net> wrote in message
news:bm0ajg$29s6$1@news.wnet.ua...[color=blue]
> Thank You again
>
> I'm not using ActiveX now.
> objEditForms is a collection to store refs to all instances of created[/color]
Forms[color=blue]
> .FillValues is Form method but we can skip it. It is not important
>
> If You are going to check smth do next:
> 1) create a form with a subform
> 2) create a code that can be visible outside mde that creates an instance[/color]
of[color=blue]
> this form
> 3) compile all above to mde
> 4) create other mdb, use this mde as reference
> 5) use code from mde to open an form
>
> The main difference is next:
> I'm not using DoCmd.OpenForm. In case of DoCmd.OpenForm all work
> but I have only 1 instance. But I'm trying to have many
>
> illya
>
> "Albert D. Kallal" <kallal@msn.com> wrote in message
> news:xaFgb.38800$9l5.1364@pd7tw2no...[color=green]
> > "Illya Havsiyevych" <gavsi@ukr.net> wrote in message
> > news:blv2d2$1h2s$1@news.wnet.ua...[color=darkred]
> > >
> > > ....
> > > Dim objForm As New Form_frmParentFormWithSubForm
> > >
> > > objEditForms.Add objForm
> > > With objForm
> > > .FillValues
> > > .Visible = True
> > > End With
> > > ....
> > >[/color]
> >
> > I think the above should work just fine. Am I to assume that[/color][/color]
objEditForms[color=blue]
> is[color=green]
> > a collection?
> >
> > Also, .FillValues. Is that a custom method of the form (ie: a public
> > function?). How does that code work?
> >
> > I don't see anything in the above that would case a mde not to work, and[/color][/color]
a[color=blue][color=green]
> > mdb to function. The only difference between a mde and mdb is that
> > un-trapped errors in a mdb re-set all your global vars. Perhaps you have[/color][/color]
a[color=blue][color=green]
> > un-trapped error in the mdb that resets your values (those values don't
> > re-set in a mde...but remain intact even AFTER un-trapped errors).
> >
> > I would spend some time checking the above.
> >
> > However, if you are really insisting on using a activeX control, then I
> > would suggest you ask your question for which activex control to use in[/color][/color]
a[color=blue]
> VB[color=green]
> > group, and not a ms-access group, as most here don't use he activeX[/color]
> controls[color=green]
> > due to the problems of references, and the need for a installer. I don't
> > know which activeX contorl is the best....but what is stopping you from
> > trying a few?
> >
> > --
> > Albert D. Kallal (MVP)
> > Edmonton, Alberta Canada
> > kallal@msn.com
> > http://www.attcanada.net/~kallal.msn
> >
> >
> >[/color]
>
>[/color]

"Illya Havsiyevych" <gavsi@ukr.net> wrote in message
news:bm0e37$2c03$1@news.wnet.ua...[color=blue]
> I'm sorry very much,
> Just subform work Ok
> The subform with bound data table gives error[/color]

I done the above many times. Some with 3 or even 4 sub forms and a LOT of
code. The multiple instances all functioned as usual.

You should note that the on-load event fires when you create the instance of
the form.

That means the when the following line of code is executed, the on-load even
fires:


Dim objForm As New Form_frmParentFormWithSubForm

Since all class objects fire their initialize event when using the new
keyword, often, many developers will NOT use a the new keyword as a result
(it is considered bad programming practice....and one I am also guilty of).
In fact, if you reference any property of the "base" form object, and that
form object is NOT loaded, then again the on-load event fires. As a result,
I would check any initialize code and make sure NONE OF YOUR CODE uses
references to base forms objects like:

Form_frmParentFormWithSubForm.FillList


If you need to control when the on-load event fires, then don't use the
"new" keyword, but use:

Dim objForm As Form_frmParentFormWithSubForm


...... some code here.....

Then...

set objForm = New Form_frmParentFormWithSubForm

The on-load event will fire at the above point, and not at the "dim"
statement.
[color=blue]
>
> I created recordset by VBA and bound it at Form_Load time
> and became Ok[/color]

Hum, you should not have to do that...but ok....

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
kallal@msn.com
http://www.attcanada.net/~kallal.msn

Thank You

"Albert D. Kallal" <kallal@msn.com> wrote in message
news:1KWgb.48136$6C4.45639@pd7tw1no...[color=blue]
> "Illya Havsiyevych" <gavsi@ukr.net> wrote in message
> news:bm0e37$2c03$1@news.wnet.ua...[color=green]
> > I'm sorry very much,
> > Just subform work Ok
> > The subform with bound data table gives error[/color]
>
> I done the above many times. Some with 3 or even 4 sub forms and a LOT of
> code. The multiple instances all functioned as usual.
>
> You should note that the on-load event fires when you create the instance[/color]
of[color=blue]
> the form.
>
> That means the when the following line of code is executed, the on-load[/color]
even[color=blue]
> fires:
>
>
> Dim objForm As New Form_frmParentFormWithSubForm
>
> Since all class objects fire their initialize event when using the new
> keyword, often, many developers will NOT use a the new keyword as a result
> (it is considered bad programming practice....and one I am also guilty[/color]
of).[color=blue]
> In fact, if you reference any property of the "base" form object, and that
> form object is NOT loaded, then again the on-load event fires. As a[/color]
result,[color=blue]
> I would check any initialize code and make sure NONE OF YOUR CODE uses
> references to base forms objects like:
>
> Form_frmParentFormWithSubForm.FillList
>
>
> If you need to control when the on-load event fires, then don't use the
> "new" keyword, but use:
>
> Dim objForm As Form_frmParentFormWithSubForm
>
>
> ..... some code here.....
>
> Then...
>
> set objForm = New Form_frmParentFormWithSubForm
>
> The on-load event will fire at the above point, and not at the "dim"
> statement.
>[color=green]
> >
> > I created recordset by VBA and bound it at Form_Load time
> > and became Ok[/color]
>
> Hum, you should not have to do that...but ok....
>
> --
> Albert D. Kallal (MVP)
> Edmonton, Alberta Canada
> kallal@msn.com
> http://www.attcanada.net/~kallal.msn
>
>
>[/color]