Display records from excel or database

[techguy86]

I’m creating a gui to reference static data fields from flash cards. How would you recommend I do this? Excel like table, database, etc.? Or all internally.

[Nine]

Hard to say with so little information.  Display a few samples of the data you got, so we get a better idea of what you're aiming at...

[jchd]

Also provide the typical data volume range expected and sample queries you want to run. An SQLite database might be convenient.

[techguy86]

Depths 0-11 measured in inches and mm

Spaces 1-12 measured in inches and mm

I want to have the ability to filter by Punch Series, etc, basically any field. So if you have a depth of 1mm, show all records with a depth of 1mm in any space. etc. Also, filter by insertion direction...also, filter by number of spaces. Not every record will use 12 spaces and not every record will use 11 depths. there maybe hundreds of depths. 104 records minimum

Sorry for the delay. 

Edited December 26, 2023 by techguy86
Records update

[Nine]

Still would appreciate to get a sample of the raw input data contained in the flash card.  But based on the description you previously showed us, I would probably go with some GUI list view (maybe virtual if volume is large enough).  But the source could be a SQL DB or just a simple 2D array, that will also depend on the volume.

 

[techguy86]

Does this help?

[techguy86]

If I find a key and don’t know which flash card to use, I can filter by cuts, or insertion direction, single sided, double sided, etc. 

[jchd]

An SQLite database would definitely help. All known data will reside in a single external file easily queried on any combination of criterion.

[techguy86]

Sounds complicated, but hopefully there’s some examples in the AutoIt help text.

[jchd]

Focus first on your data, do NOT start coding anything! List all entities you'll have to handle and determine their relationships.

Use a good SQLite manager (I warmly recommend SQLite Expert personal edition, free) and start by creating your tables. Fill in a handful of items so you can play a little. Create some of the queries you'll need, detect issues and adapt the DB schema accordingly.

Only when you're reasonably confident that your DB design fits every real-world need you can imagine, can you start coding something. And this step may not even prove necessary.

For instance I do electronic board repair for a living. 15k repairs in several years. All of my business fits inside a single SQLite database and I need no extra program.

[Nine]

2 hours ago, techguy86 said:

Does this help?

Yes. Could you please answer all the following questions :

1- How will you enter that data into whatever support you will use, manually ?

2- Is there XML or Json or any other data representation of those cards ?

3- How many keys (flash cards) do you intend to first load ? 

4- What is the annual growth of this ? 

5- Will you be deleting entries after awhile ?