Search options (Page 93 of 104)

Hi and Welcome to MVD,
Here is a link to a project that Dmitry (the writer of MVD) put together to demonstrate many-to-many relationships.
http://myvisualdatabase.com/forum/viewtopic.php?id=1429
It might answer some of your questions.
If not, just post another question and I'm sure there will be someone who can help.
Regards,
Derek.

Hello Adam,
Please find attached your project with the problem (as I understand it) fixed.
In your original script, you were trying to retrieve the customer details using the key of the invoiceheader table from the invoiceheader grid. 
What you need to do is get the foreign key (id_customers) off the invoiceheader table from the invoiceheader grid AND THEN retrieve the customer details using the foreign key value.
In effect, what you are doing is a 'nested select' (I'm sure there's a technical term for it!!).
Have a look at the sections that I've changed and I think you'll see why it wasn't working.
I may have missed some other bits that you might have to fix but the principle (and the code) is exactly the same.
Regards,
Derek.

Hello Adam, EHW,
I was looking at your password issue again and trying to use standard MVD as much as possible.
So I've gone with using the usual tablegrid / edit forms for the users / passwords.  This allows you to have more than one user (which you said earlier was something you might want) and adding, changing and deleting needs no additional code.
And to reduce the script, I've used text hint functionality to reveal the passwords - just hover the mouse over the asterisks.
It's a different approach and might give you some ideas.
Derek.

Dmitry,
That's good news.  I shall go ahead and upgrade.
Can you send me the link to the page where MVD Version 3 is available for the discounted price?
Thanks.
Derek.

Hello Bulutsuzgece,
'Tablename'/'Fieldname' are not properties of COMBOBOX objects, they are properties of EDIT, MEMO and DATETIMEPICKER objects and can be selected from a dropdown list after you have defined your tables and fields (in the database tab of MVD).
'Foreignkey'/'Fieldname' are properties of COMBOBOXES and can be selected from a dropdown list after you have defined your RELATIONSHIPS between tables in the database tab of MVD.
If nothing is showing as selectable, this is because you HAVE NOT DEFINED any relationships between tables.
Creating relationships between your tables should correct this.
Derek.

Hello Adam,
As always with MVD, different ways to do it - this is probably one of the simpler options (which is why I like it - LOL!!).
Regards,
Derek.

Hi Nrmuduli,
My sql is perhaps a bit different to yours but is this any help?
Derek.

Hello All,
I know that it doesn't answer some of the questions about MVD internal messages not being in the localised language (error messages, warnings etc) but it is quite straightforward to create a multi-language application (with only a bit of extra work).  As always with MVD, there will be many ways to achieve this but attached is a small application that I made to see how I might do it.
Basically, I just overlay panels on each form (one panel per language - I have used french and english in my example).  It is quickest to get everything as you want it to look on one panel and then copy and paste the first panel (all the objects on the panel are automatically included) to the second panel and then just change the labels, text hints etc.  Then for each form, you set which panel should be visible by script, depending on the language chosen.  Using panels keeps the script simple.
My example is very basic but it perhaps shows what can be done and gives people some ideas.
Derek.

Hi Adam, EHW and anyone else,
Please find attached one option for handling refunds (using just one table to hold both DB and CR transactions, as outlined by EHW). 
It's a clone of an old project so it doesn't look too much like yours but the principle of using either different tablegrids to split off invoices and credit notes (refunds) or (as I've done in this example) using the same tablegrid with a real-time filter, is basically the same. 
I prefer this way because it's quick and easy to set up and also means you can see ALL transactions, just DB transactions or just CR transactions all on the same grid - but you could choose to show 3 discrete grids all on the same screen if you wanted.
It's just 'play data' but it should work - the script is a bit messy but most of it is just for cosmetic reasons or better ease of use for users.
Hope this gives you some ideas.
Derek.

Hi Adam,
Glad it helped.
The PC I was using when I replied earlier has MVD 2.4 which doesn't have the tablegrid 'show child records (if present)' feature.  When I saw your response, I remembered that you no longer need to use a 'search' button from MVD 2.7 onwards (I think) - d'oh!
So yes, the only issue was the missing table link.
Derek.

Hello Again,
Realised that in my earlier post, I hadn't set form1.button2 (the 'GO' button) as default which meant you had to either click it or use 'TAB' and then 'ENTER';  now as soon as you enter the ID, you can press 'ENTER' and off it goes.  Sorry about that.
In the attachment, I've also used a slightly different approach - what I call 'form cloning' (I'm sure there must be a more technical term - LOL!).  It appears as if you are working on the same form but in fact you are flipping between the two.  As I see it, there are a number of advantages:
1.  it's still standard MVD so there is little scripting (if any) to do.
2.  you can designate different buttons as 'default' on each screen which speeds the user up.
3.  you can set what fields are enabled/disabled using object properties (again, standard MVD) rather than switching them on and off by script.
Not saying any approach is right or wrong - just shows how flexible MVD can be.
Derek.

Hello Adam,
As I said in my last post, you can just replace the .visible with .enabled in the relevant lines in the script and change the object properties on the form.  Anyway, it's in the attachment.
I was confused by form1.tgprod and form1.tablegrid1 - they both show product data so wasn't sure why you have both on the form.
If you're serious about using just one form, I'd strongly advise at least the following:
1.  setting your fields to mandatory, where possible. 
2.  conditionally hide the 'save' button unless either the 'own product' or the 'purchased product' checkbox is ticked.
I say this because it is far too easy just to accidently click 'save' and create empty records (or, once you've added an 'edit' button), to create duplicates of existing records as well.  Try clicking 'save' a few times and see what happens. 
Just my opinion, for what it's worth.
Derek.