Search options (Page 68 of 104)

Hello Darek,
1.  If a field can only have 'yes' or 'no' (or optionally 'neither' as its value, you can choose to define it in your data structure as 'boolean';  use a 'checkbox' on your form and this then shows in tablegrids as 'yes' or 'no'.
2.  I put your CSV into a spreadsheet and -
  a) got unique values for categories and gave each value a sequence number (key) - this became the 'categories' table
  b) got unique values for film title / year and gave each value a sequence number (key) - this became the 'films' table
  c) added the relevant keys (id_films and id_categories) to the nominations - this became the 'nominations' table
I used a utility called SQLiteStudio (it's free) to do the initial data load (you can use MVD import routines (probably the 'correct' way to do it!) but I find it just as quick this way).
I've changed the way the number of nominations for each film and the winners for each film is processed - using calculated fields was slowing it down a bit.
I have added a (temporary) button on Form1 (see attached) called 'Raw Data' - it shows you how all the data is stored in the 3 tables in your database.  It might help you to understand how MVD (and all relational database products) works.  You can just delete the button and associated form when you don't need it any more.
Look at the screenshot in the attachment and see how the data is linked together - for example, '2001 A Space Odyssey' has an ID of 18 - then look at the nominations table in the id_films column with a key of 18 and you'll see the 4 nominations.  Look at the id_category column and follow each of the 4 keys to the 'category' table to see which category it relates to etc, etc. 
Of course, MVD does all this for you automatically but I think it helps if you understand the basic principles behind it.
Regards,
Derek.

Hi Manixs,
I suppose the 'correct' way would be to read through the images in a directory and load the file names into some sort of stringlist etc.
But if the number of images is fixed, I'd probably do it very simply as per the attached example (if you have a large number of images, use a batch utility to rename them 1.jpg, 2.jpg, 3.jpg ,4.jpg etc and then alter the script to however many images you have).
Derek

Hi Adam,
I'm rather confused as to what you're trying to achieve now.  Can you answer a couple of questions -
1.  Are you holding a starting balance against the account or is the starting balance the first entry in either the transactions or the journals tables?
2.  Why do you have separate fields for transaction date and transaction time on the transactions table  (the journal table uses 1 field (date/time)?
3.  Isn't a journal (positive or negative) just another transaction, in which case, why have 2 separate tables?
Question 3 is particularly important because if you split things over 2 tables, do you then want to see one running balance for journals and a second running balance for transactions - and if so, does the starting balance get included in the calculation for the journals running balance or for the transactions running balance (or both or neither)?  Surely you can only have 1 running balance.
Or do you want to see the running balance at any point in time using the starting balance + all of the activity from the journals table up to that point + all of the activity from the transactions table up to that point - so the running balance will always show the same whether you're looking at the 'journals' tablegrid or the 'transaction' tablegrid?   If so, I can imagine users constantly switching between the two trying to reconcile the amounts.
As always, I favour keeping things as simple as possible and, for what it's worth, I'd go with just two tables (account and transactions) and use transaction types of 'deposit', 'withdrawal', 'journal-in', 'journal out' and 'starting balance'.  Your transactions table will inevitably end up with fields that are relevant to only certain transaction types (but that's no different to how it is now with fields for withdrawals, for deposits etc) but at least it will be easier for everyone to work out what's going on..
Derek.

Привет,
В варианте 1 я использовал SQLiteStudio для заполнения таблицы «статус» - так было быстрее.
В приложении приведен пример, поэтому вы можете ввести значения для таблицы «status».
С вариантом 2 не было никаких проблем, потому что статус изменяется в скрипте.
Derek.
.
Hello,
In Option 1,I used SQLiteStudio to populate the 'status' table - it was quicker to do it like that.
Attached is an example so you can enter the values for the 'status' table.
With Option 2 there was no problem because the status is changed within the script.

Hi Adam,
Form1.tgjournal should now be showing the running balance at the row level.  Form1.tgaccount shows the current balance as it did before.
You can enter journals for earlier dates (or same date but different times) than the most recent journal and the formula will automatically recalculate the running balance for each row.
Derek.

Hi All,
You could also try 'setfocusnextcontrol'.  Please see attached example.
Be careful if you have buttons on the form - I'd set their 'default' and 'tabstop' properties to 'false' otherwise 'enter' will be interpreted as a 'click'.
Regards,
Derek.

Hello,
Please see the attached example and screenshot1.
The button that has the 'default' property set to 'true' is the button that automatically gets clicked when the User presses 'Enter'.
Check that any other buttons on the form are set to 'false' otherwise it might not do what you want.
Regards,
Derek.

Hi Eyeman and TC,
Rather than using a script to show the patient's name (first, middle and last), why don't you concatenate those fields in the drop-down list itself (see screenshot1 in attachment epl2);  this has a number of benefits.
1.  no script
2.  you can search the drop down list not only by PID, but also by any part of the name so picking the correct patient in the first place is much easier.
3.  the patient and all the details selected in the drop down list stays visible.
Please see attached (epl2) a simplified example of what you might do (you can also search within the drop down list by date of birth and the number of outpatient visits made).
I also attach an alternative version (epl1) which is a much more traditional approach (starting with the patient, then drilling down into the outpatient visits record);  doing it this way, you are forced to maintain the link between the patient and the outpatient visit which I believe is a much better approach (and much simpler), but maybe there is a business reason why you need to 'de-link' patient and outpatient visit.
Derek.

Hi Adam,
What version of MVD are you using?
I've noticed formatting problems with 5.4 so have switched back to 5.1 for the time being. 
You can probably get round it by re-writing the script but I don't think that's really the way to solve version compatibility issues.
Derek.

Hi,
I think the problem might be the 'datein' field, originally defined as 'date/time' - when you change it to 'date' the code works fine and overdue items are coloured red.
Also, remember that when you are writing scripts that reference specific columns, columns (and rows) start at 0, not 1.  So you needed to change your [2,i].color to [1,i].color etc etc because you moved the 'datetin' column.  Also, your 'hotspot' columns needed to change because you'd added a new column.
You could also  colour the days overdue column - that way you can easily see whether an item was late processed irrespective of whether it has now been filed, printed or 'for dissemination'.  Just a thought.
Derek.

LOL -  I reckon your money's safe!
Just checked and realised that I'd forgotten to switch the tablegrid colouring back on - here's the corrected version if you need it.
Derek.