Attachment 179775
it can add columns as checkbox,button,combobox,textbox,image,etc..
Printable View
Attachment 179775
it can add columns as checkbox,button,combobox,textbox,image,etc..
and this OGrid control in Microsoft Access
Attachment 179776
Is there any OCX like this?
Attachment 179777
:confused: anyone can help ?
You can check these grid controls to see if anyone can do what you want:
VBFlexGrid
vhGrid
LynxGrid 1 or LynxGrid 2
i think there is a way to put vb.net ocx on vb6 forms
make a vb.net com dll,ocx,use on vb6 form1.frm
that's good
If it is acceptable to have it in a separate form, you can load the form via Com interop. I've not embedded a .Net control in vb6 but I know it can be done. Can find the link if its useful
thanks a lot
The BEST ActiveX grid is TrueDBGrid:
https://www.grapecity.com/componento...ontrol-activex
Using this grid you can make anythings.
If you were to be spending money (TrueDBGrid), you should check out the iGrid from 10Tec
Much cheaper.
Fully functional Trial, that never expires (we get nag msgbox instead)
Tons of examples can be downloaded.
The author responds well to questions, and if you had a need that it did not meet, he can add it, if it is worthy.
Rob
PS it is based on the free SGrid, which they have debugged, and enhanced the .... out of it.
I use the free SGrid2, which meets all of my (more meager needs)
Here is a link to the FREE SGrid2 -
http://www.vbaccelerator.com/home/vb..._2/article.asp
I cannot connect to the 10Tec site for some (very strange) reason.
I have connected numerous times over the last decade, without problems.
They freely allow the download of the Trial,that I mentioned above.
I could get the latest (that I have) to you fairly easily.
thx for reply:)
thanks for your advise
VB.Net doesn't have a concept like OCX. A control in .Net is just like any other object. You don't need any kind of specialized library to export one. You can export it just as you would any ordinary windowless object.
Also, it is very much possible to use COM Interop to export an entire Form from .Net and use it in a VB6 application and it's actually very easy to do. Siting a .Net Control onto a VB6 Form/Usercontrol however, is something different entirely. I've never explored that but I don't expect it to be easy. I'd advise to implement the entire Form in .Net and export that. It's much much easier to do it that way.
We are using many mixed libraries in our legacy projects - VB6 main EXE with reference to .NET where some UI is implemented as form. Also I've created many .NET libraries with many exposed COM objects for some functionalities that are missing in VB6 and are much easier to implement in .NET.
There is no problem to choose proper projects structure where VB6 app (exe) can use shared VB6 data layer. Same shared VB6 library can be used by the .NET library to get some info that will be shown in the form.
So for the OP the proper approach is what Niya said:Quote:
I'd advise to implement the entire Form in .Net and export that. It's much much easier to do it that way.
I would prefer to keep it simple and not have the .Net side import anything. All the importing would be done from the VB6 side. If I were doing this, I would create a class in .Net with methods that allow you to pass information from the VB6 application and the .Net class would internally create the Form using the information that was passed through the object's methods on the VB6 side. The .Net objects would have no awareness whatsoever that they were being called from a VB6 application.
Niya, in my case there was quite complex data management and logic written in VB6 so without way to call back it was unusable. On form shown event it shows initial state, user clicks here and there, .NET "sends" info to VB6 (call sub or function) and gets new info back.
Anyway, that mixed approach works. And it can become more complicated - in .NET form (called by VB6) is shown browser control (CefSharp) which shows some html widgets which are generated by web service, but this is another story. Sounds like total mess but it is fun when you get it working.
lol....this sounds like quite a monster. Yea, things like that can be expected with large-scale production applications and sometimes we can't help but avoid complexity. However, in most cases where the needs are simple, we should always strive to keep things simple.
Thanks for all replied users ,Finally , I choice the FlexCell at now.
FlexCell is an excellent product. Its features are not the most powerful, but it can satisfy most scenarios. In addition, it's extremely cost-effective, and its price seems to be only 10%-20% of other similar products.
Many years ago, I bought a license for farpoint spread for US$800. At the same time, I also bought a set of FlexCell for 300RMB (US$40). Both products performed very well.
I just released a sample on applying COM Interop to mix VB6 and VB.Net. You can check it out here if you're ever interested.