Search options (Page 69 of 104)

Hi,
To turn the cell yellow based on status = 'Filed'  and override the date criteria, try it like this (see attached).
Derek.

Hi,
Like Thierry, I too had a project from a couple of years back that was a bit similar.
So I've changed a couple of the forms and made the data more compatible with your requirement (please see attachment).
It won't be exactly what you need but I think there are examples of how to do similar things so you can apply them to your specific situation.
There is no log-in security, but you could just bolt on the forms from your existing project.
On this project, I didn't colour code the grid - rather I have a column that show the number of days that a document has been on the system and you can sort or filter on that instead.  Or you could do both!
Also, it uses what I call (probably incorrectly!) 'hot-spots' where you click on specific cells to make calls specific to the value in that cell.  So to view a specific document, click in the actual cell where the document location is held.  Or to view a document's history, click on an actual cell in the 'Current Status' column etc etc (people I knock stuff up for like the 'interactive grid' approach!).
Hope this gives you some more ideas,
Derek.

Sorry, but I can't quite work out what you're trying to do.
Can you attach your program?

Hi,
Yes, I would always use 'onchange' for something like this.
You might also think about putting an 'onchange' event against 'selling price' and 'quantity' as well because these are also used in your calculation and you could change these values but it wouldn't automatically recalculate until you changed (or re-entered) 'percentage gain'.
Rather than repeat the calculation on each 'onchange' event, I put it in my own procedure (because it's easier to maintain - if you change the calculation, you only have to change it in one place in the script).
Derek.

Hi Terry,
Is this any good to you (see attached).
It's part of an old project but it sounds like it's the same sort of thing that you're wanting to do.  You can make deposits / withdrawals out of sequence (different days, same day different times etc) and the running balance should always recalculate.
Derek.

Hi,
In your script, first declare your variable
var  variable1: string; 

and then
variable1 := form1.edit1.text;

Derek.

Hi,
There are a couple of things to understand when using calculated fields.
Calculated fields only exist while your program is running - as soon as the program closes, the calculated fields are gone.  For example, you would save someone's date of birth but you wouldn't save their age - that would be data redundancy.  Instead, you calculate their age every time the program runs using a calculated field so it is always up to date, but as soon as the program closes, their 'age' is gone.
So you are correct when you say that there are no instructions DIRECTLY relating to calculated fields in the script.  But what the script does is
1)  run a search when the program starts so that all the columns in the tablegrid are populated - including calculating the calculated fields.
2)  when any data is saved, the calculated fields need to be 're-calculated' - this is what the 'dbupdate' statements are doing in the script.
So when you removed the script, the calculated fields didn't appear because you removed the instruction to calculate / re-calculate them.
I hope I've explained that okay.
I've attached the project again with some comments in the script that may help.
Regards,
Derek.

Hi Thierry,
Nice one!  Never seen it done like that before.
Kudos!
Derek.

Hi g0dmenuelz,
As Manixs suggests, you could add a second numeric column, hide it and then sort on it.
But a simpler trick would be to use 2 digit numbering - instead of 1, 2, 3 etc, use 01, 02, 03 etc.
Obviously if you have more than 99 search results, you need to use 3 digit numbering.
I think it looks better anyway because the numbers and the text 'line up' (just a personal preference).
Derek

Hi,
I would use 3 tables as follows:
1.  Customer (basic information)
2.  ReceiptSummary
3.  ReceiptDetail
The relationship between Customer and ReceiptSummary is 1:many.
The relationship between ReceiptSummary and ReceiptDetail is 1:many
This allows one or a number of customers to sell one or a number of items on one or a number of different days.
Please have a look at the attached example and see if it helps.
Regards,
Derek.

Hi Adam,
I wrote the attached a while back now - perhaps it's the sort of thing that you're looking for.
It's nothing fancy - I just needed something that I could quickly jot down notes/reminders for without all the bells and whistles you get with most 'reminder' programs.
Regards,
Derek.

Hi,
The exact calculation depends on how you're holding your data but the syntax is something like the calculated field in the attachment.
Derek.