Search options (Page 80 of 104)

Hi Alex,
I'm afraid I'll have to pass on how to print the chart together with the data;  reporting is one of the areas that I'm pretty weak on (there doesn't seem to be much call for print-outs with the stuff that I'm asked to write). 
Feeble excuse, I know (LOL!) and I should take the opportunity to get up to speed but I think it would take me quite a while.
Maybe someone else who's worked more with charts/reports will have a few ideas.
Derek.

Hello Alex,
In the script, just add the line
  Chart.View3D:=false;   
You could actually remove the legend as well, as it is now simply repeating the information that displays against each slice of the piechart.  You can do that with the line. 
  Chart.legend.visible:=false;
Obviously, in some examples and with lots of 'slices' it starts to get a bit impractical, but it's something to bear in mind.
Both these options are in the attachment.
Derek.

Здравствуйте,
Я не могу запустить проект, потому что вы используете удаленную базу данных.
Но одно я не понимаю -
on frmadmin, editklass определяется как tablename 'test' и fieldname '123', но в tablegrid2 он определяется как klass.nomera & litera
Возможно, это имеет какое-то отношение к вашей проблеме (см. Скриншот)
Извините, если это неясно - я использую переводчик Google.
С Уважением,
Derek.

Hi Alex, Hi Jean,
You have a good memory Jean - I don't remember writing it - LOL!  But now you reminded me, I have managed to find it and add it to the attachment.
So, in the attachment are actually 2 examples using checkboxes.
The first example is more simple, using standard MVD with no script
The second example has a script to keep sub-totals and things like that and it uses a slightly different style / approach.
Personally, I find check boxes are okay if you have a small number of set alternatives (male or female, small, medium, large - that sort of thing).  Also, it can get a bit confusing if you have more than a couple of checkboxes and they 'allow grayed' as well.
If the options are more numerous or liable to change, then I'd probably go with comboboxes.  But it really depends on the application.
Hope this helps but if not, get back with some more details about what you're trying to do and I'm sure someone can give you some ideas.
Regards,
Derek

Hi There,
If I understand you correctly, then yes, it's possible.
Please have a look at the attached.
There is a bit more to the script than is necessary to cover your question but it addresses a couple of extra scenarios.
Using the example in the attachment
1.  When a student record is created, a .txt file gets automatically created (using the student's name as the file name).
2.  The contents of the .txt file are displayed within a memo field on Form 2.
3.  The contents of the .txt file can be edited within MVD and the changes written back to the .txt file.
4.  The contents. of the .txt file can, as usual, still be edited outside of MVD.
Please note that memo fields only support .txt files so if you want to preview anything else (ie with formatting, with pictures etc), then the better option is to make external calls (ie the call is made from within MVD but you preview it outside of MVD).
Hope this helps,
Derek.

Hi Vasco,
I believe there are Delphi commands 'sendtoback' and 'bringtofront' but I don't think they are supported in MVD.
When I want to bring objects to the front (either completely (so one object totally hides the other) or partially overlapping (so both objects remain visible at the same time)), I make the objects visible / invisible as required.  Perhaps there are other ways as well.
Please see the attached as an example (click on the various coloured boxes to see them change).
Maybe this helps,
Derek.

Здравствуйте,
Это то, что тебе надо?
Сценарий не очень хорош, но он работает!
Возможно, Дмитрий знает лучший способ.
Надеюсь, поможет.
Derek.

возникла проблема при использовании кнопки «поиск» - теперь исправлено.

Здравствуй,
Это показывает часы и минуты. Также вы можете сделать это либо с вычисленными полями, либо со сценарием.
С Уважением,
Derek.

Hi,
I would do it this way (by script rather than sqlquery - see attached) but there are probably a few other ways too.
Regards,
Derek.

Hi Tony,
With projects like yours that I've done before (3 tier hierarchy - customers - appliances - results), I've often been asked for a 'total view' all on one screen.  It might be of interest to you so I've added this sort of view to your project.  It's not as 'seamless' as it should be because I didn't want to mess up your existing project too much, but I hope you get the idea.
I've also created a calculated field on each table to do 'free format' searches (users often don't know which field they might have put data into!). so rather than have multiple discrete search fields, they can just type anything in to one search and it scans across all fields (hope that makes sense).  For example, in the 'appliance' search, you can enter maker or model or serial no' or location etc etc.
All of the above can be done without using a script (although I've added a few lines, just to automate things and make it more user-friendly).
Hope it helps,
Derek.

Hi Tony,
I use a free utility called SQLiteStudio. 
Once downloaded and installed, if you click the sqlite.db that gets created when you first run your application, it opens in sqlitestudio showing all the structures, indexes etc. 
Among many features, there is, for each table, a data view and that is where you can see the 'raw' data and how the relationships between tables are being maintained (or not!).  I find it very useful for tracking down problems (the clue is almost always in the data!!), but it also gives you a much better understanding of how MVD actually hangs together and what it's doing 'behind the scenes'.
Using SQLiteStudio, it was very easy to spot that the relationship between 'test' and 'customer' wasn't being maintained.  I referred to the appliance table to find out the correct customer id for each appliance and then went back to the 'tests' table and manually copy and pasted in the missing keys (it's actually a lot more straightforward than it sounds!)..
If you don't want to use SQLiteStudio, you can also do a 'datacheck' yourself within MVD - please have a look at the attachment where I've added a 'datacheck' button to your main screen.   It's a quick and easy way to 'sight-check' your data and if you make your 'datacheck' tablegrids editable, you can fix the problem there and then. 
When you're happy with the quality of the data (typically just before you roll your application out), you can then delete the datacheck form and button (although I tend to just make the button invisible so that the facility is always there in case of future problems).
Hope all of that makes sense,
Regards,
Derek.