Re: sqlite3, database views and db.gb.form controls. Does it work?
Posted: Friday 5th February 2021 11:21pm
I'm glad that you are making changes to the way I do things as it's the best way to learn.
It was only ever meant to be an example to show all the aspects of data management without any dataview controls.
One of the reasons I abstract the data Get/Add/Change/Delete to a class, is that I can call that class anywhere in the application
to get access to that data. For example, on the Main (start up) form, you can set up a quick view of say:
All the Mount Types you have available.
Add a ListBox control to your main form.
Create the following subroutine.
Call the subroutine from your Form_Open event.
Lens Form
It's a busy form. Lots of variables in the lens data set. I did toy with the idea of using a TabStrip control, with each tab containing
lens elements controls that 'belonged' together but I don't know enough about lenses to sort out the relevant
information into any sensible sets/families.
One thing with using any tabbed control - TabPanel or TabStrip, when you are validating data input for the user,
make sure that you display the panel with the error. There is nothing worse that getting a validation error and
having to hunt through various tabs to try and find it.
It was only ever meant to be an example to show all the aspects of data management without any dataview controls.
One of the reasons I abstract the data Get/Add/Change/Delete to a class, is that I can call that class anywhere in the application
to get access to that data. For example, on the Main (start up) form, you can set up a quick view of say:
All the Mount Types you have available.
Add a ListBox control to your main form.
Create the following subroutine.
Call the subroutine from your Form_Open event.
Private Sub DisplayMountTypes()
Dim Mnt As New Cls_Mounts
Dim TmpInt As Integer
ListBox1.clear
For Tmpint = 1 To Mnt.RecordCount
Mnt.GetRecordData(TmpInt)
ListBox1.Add(Mnt.MountName)
Next
Mnt = Null
End
Lens Form
It's a busy form. Lots of variables in the lens data set. I did toy with the idea of using a TabStrip control, with each tab containing
lens elements controls that 'belonged' together but I don't know enough about lenses to sort out the relevant
information into any sensible sets/families.
One thing with using any tabbed control - TabPanel or TabStrip, when you are validating data input for the user,
make sure that you display the panel with the error. There is nothing worse that getting a validation error and
having to hunt through various tabs to try and find it.