Maintain Text typed in Text Box Cells Visible. (Page 1 of 2)

Hello heribertom6466

What is the goal of this text ?

Will this text change all along your application ?

If not, Form1.TextBox1.Text := 'my text'; could be enough.
Is this what you want ?

JB

Hello JB,

I'm making an inventory form for 4 vehicles and want to keep the inventory database separated. Since
the vehicles carry different types of equipment.

for example:

At the top of the image I typed in the trucks information.
I would like for that to stay in the cells  and be visible.

The inventory will be going to the Table grid as normal.

Thank you,
Eddie

I still do not understand where / how you want this information to be displayed, could you create some kind of photo-montage?

I think I understood what you want to achieve, could we see how your database looks like please? Click on the button next to "New Table" in MVDB and send a capture of it.

I think you are missing the correct use of relationships and comboboxes or you are not using "Show Record" property for your button. There might be a design issue as well

Why so many Truck tables?

The view could be cleared up by moving the tables in order to clarify the output !

You were maybe misled by the design of a table, try to imagine that the lines are actually columns in an excel sheet.

The purpose of a database is to gather all information of same kind at the same place.

Designing the tables and relationships is the most important part of your database, you have to think about what you want to see, how you want to see it, how information should interact and how you could do it in the simplest way possible. Always think KISS ( keep it simple stupid) and avoid redundancy.

Remember that in a database, a record is a line with several columns, a relationship is the id of another line in another table. We use relationships to avoid information redundancy and to ease the maintenance by splitting the information. It is easier to maintain a small table (adding, removing columns, modifying content meaning, etc...)

In your case, you only need one table Trucks and maybe draw something on the paper to clarify your view.

All your trucks will be in same table but can have different properties

What is the departure point? Trucks? Accidents? Vehicule input? Vendors? Parts?

If you struggle too much, you could also submit your project to the forum and we will help you.

I got some sleep, drank lots of coffee and went at it again with this database. By the way it's kicking my but!!
I had to "KISS" like Tcoton explained. LOL well it's working for me...
which includes 15 forms and managed to get it down to 5 tables. LOL
what a difference.

I'll keep you posted if I managed to work it out. :-D

Eddie

I had a look at your project but it is unclear what you want to achieve here!

Why 2 buttons on start to do the same thing? Why creating an inventory with no possibility to see it? It is a bit confuse for me

Ok, I think you did not get what a database is actually

You want a truck inventory, then instead of thinking the trucks should be separated, try to imagine your database as a big garage. Would you fit the garage inside each vehicle or the opposite?

I will try to design something very basic with what you sent above.

This is how I designed the relationship between my tables.
This possibly could be a problem with my Table grids.

Eddie

In new diagram, there is a id_Trucks relationshipship linked with nothing...

Hello,

I've been doing research and database schema and found out that I wasn't possibly explaining my self correctly.

I want to design tables for inventory in multiple locations.
If I'm not mistaken product look up would best define this issue.

What do you think?

Eddie