how to do this

Hello.

You just forget to specify TableName and FieldName properties for DateTimePicker1 and DateTimePicker2 component.

TableName = Product
FieldName = Expiry

Please describe your question in more details.

ehwagner,

Thank you! you got it right on the mark!

Kudos!

Anakin

Check the attached and see if that is what you want.

It sounds like you may have inserted another column in front of the product name in the tablegrid. If you did then you need to change the FOR LOOP to point to UNITS column in the tablegrid.

Whatever the column number is for UNITS beginning with Column 0 then replace the digit 1 below in Cells[1,i] and Cell[1,i] with the appropriate number. In other words, if the UNITS column is now the third column in the tablegrid, then you want to replace the 1 with 2.

If StrToInt(Inventory.TableGrid1.Cells[1,i]) < 1 then
           Begin
              Inventory.TableGrid1.Cell[1,i].TextColor := clRed;
              Inventory.TableGrid1.Cell[1,i].FontStyle := fsBold;
           End;

Anakin,
Thank you for your kind words. When I came to MVD I knew nothing about the development system and I knew nothing about Pascal except that it is essentially an old development language, meaning it's been around for awhile. However, I've had experience with other development systems and programming languages so my learning curve was very small. I just adapted the same techniques to MVD. For me I learned MVD by going through the videos and online help documents developed by Dimitry http://myvisualdatabase.com/help_en/. I relied on the forum heavily in the beginning and still do. I have also used Delphi Basics website. http://www.delphibasics.co.uk/    I have used SQL reference websites sometimes for assistance with complex SQL statements. For SQL websites you need to make sure the syntax is for either SQLite or MySQL, whichever you are using. There are subtle differences among databases.

The forum is an invaluable resource especially when you are stuck on something. Don't hesitate to ask. There are a lot of people on here who can help. One is Derek who is a very active member on here and he has helped me. I call him the "Master of Non-script Solutions". :-)  I say this out of respect for his knowledge. Obviously, most projects cannot go without some scripting and he has provided significant help with that as well. Dimitry who is the author of MVD is invaluable on here. He can help where other people are not able to. There are a lot more people on here and I don't want to start naming names because I don't want to leave anyone out. As I said before, don't hesitate to ask for help.

I would highly recommend building a code snippet database as soon as you can. Doing so will help you tremendously as you are learning. It can become a very useful resource as a reference tool. Most of the snippets I have came from the forum as new versions come out and from things people have posted that may not be in the help system.

One final thing, I really do not feel that I am an expert on MVD, but I try to help people whenever I can with what I know.

Hi Anakin, Hi EHW,
Can you upload the most recent version of your project?  But without looking it it, I would guess it's because
1)  you have an incorrectly specified join between tables.
OR
2)  you have specified the wrong 'main' table in your tablegrid
On a more general point, the only thing I would add to EHW's comments made earlier (all of which I agree with), is that you really need to have a basic understanding of how a relational database 'works';  good database design is just as important as good programming and without it, you can quickly run into problems.
Derek.

Hi Derek & ehwagner,

I heeded your advise to check whether my project has good database design. And I found out that what was lacking was to make my other tables (classifiction and variants) linked (relationship) to my sales table. That did the trick.

I learned today that the more simple the database structure is, the better. Simplicity is key to good database?

Thanks for your tips guys. I will study this stuffs and catch up with you. Please send me more links to study.

Thanks to you both!

Anakin

Hi Anakin,
It's not possible to download your project without permission using a google account.
Can you make it available without requiring permission or as a simple download using something like 'dropbox'?
Derek.

Anakin,
See attached for the revised fixed project. Classification and Variant are correctly defined as a relationship to Product, so you really should not have it related to Sales. But in order to bring in those two fields into the Sales tablegrid I created calculated fields to retrieve the respective names. Keep in mind that calculated fields are not real fields so it is not duplicating data in the Sales table.  Also, the controls for these two fields in the NewSale form are defined as ReadOnly.  You cannot change them in this form because they belong to Product, not Sales. Hope this helps.

I just noticed that you asked about placing the Payment and Change in the tablegrid. All you have to do is define them in the Sales table, then put the definitions in the object Inspector of the Sales form. Don't forget to include them in the Save action.

Anakin,
See attached.  I added Payment and Change fields in the database definitions for the Sales table, placed the new fields in the AllSales tablegrid, changed the NewSale form Object Inspector for each field to point to the corresponding table field, included the new fields in the Save action, and put in script to colorize table rows with no payments to red.