Search options (Page 88 of 104)

Hi Adam,
I was able to recreate the problem you found.
I think it was when a deletion was done from the 'all refunds' list rather than having first selected a PI or SI and then deleting. 
So the easiest fix is, when you're in 'all refunds' mode, to hide the 'delete' button and only re-show it when a specific PI or SI has been clicked.
I've done this and given it a good test and it seems to be fine now.
Apologies for missing that (school boy error - or in my case school grandad error - LOL!).
Derek.

Hi Manixs,
I ran out of time yesterday to finish this off.
Here is the version with formatting (but the principle of how to keep a running balance is the same as the old version).
Regards,
Derek.

Hi David,
Nice to hear from you again too.  New Zealand - very nice!  UK here, for my sins - LOL!
Thanks for the link;  I remember seeing the post ages ago but only thought it could be used as some sort of 'countdown' to trigger a one-off event.  There a couple of  programs I've got where it will come in very handy.
Best Wishes,
Derek.

Hi Knobby,
You are 95% there.
By default, when you set up searches in MVD, it wants you to enter an exact match.
However, you can change this in the object properties of the search edit field (please see attached screen shot).
For example, set the filter to be s% to match from the start of what you type, %s% to match a character string anywhere in what you type etc etc.
Also note that you could have typed your search with the '%' wildcards yourself and it would have worked but it's not very user-friendly.
Hope this helps.
Derek.

Hi Adam,
So something like a visual prompt on the purchase and sales invoice grids that there are refunds?
Adding this has also enabled me to simplify the orphaned refund problem - no need for messages or anything now so it's reduced the size of the script by a few lines - LOL!
Please find attached.
Derek.

Hello Bo,
It works fine for me (unless you're meaning something else).  Please see attached project and screenshot..
Perhaps it's a Version issue (I've tried it back as far as MVD3.2 and it's still okay).
Regards,
Derek.

Hi Adam,
No problem - it's an straightforward fix.
If you change the name of the 'Show Refunds' button you need to change it in the script (which you have found and done) but you also need to change form1.edit1.  This uses the 'Show Refunds' button to do an incremental search so have a look at the object properties for form1.edit1  (Increm.Search) and make the same change there (click the drop down on the Increm.Search property and you should see your renamed button in there.
Fingers crossed, you should be working again.
Derek.

Hi Benjamin,
If you have relationships set up between tables, this shouldn't happen.
If, however, you only have one table or you have tables with no relationships, you can still populate your own combobox with distinct values from the column you are interested in.
However, doing it this way, I've found that you need to add a small extra step which is to then copy the distinct value you have selected from your combobox into an edit field.  You then use the contents of the edit field in your search.   Maybe others know of a different way to do it.
Anyway, please have a look at the attached example and hopefully this helps,
Regards,
Derek.

Hi Knobby,
Is there any chance you can upload your project and then someone will no doubt take a look at it (that's when you end up with 5 different solutions because we all have our own ways of doing things!).
But from what you've described, it sounds like you're missing an 'end;' at the end of one of your procedures;  just putting a ';' on its own will simply move the error down to the next line.  Typically, the format for any procedure is
procedure xyz;
begin
  abc
  abc
end;
This would account for both the error message you get and the grey box showing.
Derek.

Hi Knobby,
Yes, you can change all of that - you can even replace it totally with your own menu structure. 
But it requires a script which, having read another of your posts, you're not at the stage of wanting to get into (which is perfectly understandable if you're quite new to MVD).
In the meantime, if you just want to remove the 'menu bar' completely, there is an option in the form properties called 'border style';  set this to 'bsdialog' (see attached screenshot).  Please note that you do this for the main form (ie the first form that is opened when running your project) and all other forms then take the same style.
Hope this helps,
Derek.

Hi Knobby,
You could try something like this (see attached).  It's pretty basic but might give you some ideas.
Regards,
Derek.

Hi Adam,
Two things stood out when looking at the 'tgrid field display' project you attached in your latest post:
1.  I'm not sure why you need a separate 'refunds' table - isn't a refund just another transaction type (you already have purchase and sales transaction types on your 'invoices' table). 
Also, as the structure of the 2 tables is basically the same.  I think storing your different transaction types in 1 table would simplify things a lot;  I would probably rename 'invoice' to 'transaction' and create a related 'transactiontype' table (with fields 'type' and 'dbcr') and see if that approach streamlined things.
2.  I noticed that in your script, if you create more than 1 refund transaction against the same purchase or sales invoice, this actually creates a duplicate purchase or sales invoice record;  maybe you are already know this.
I am aware that you are probably just 'trying things out' at the moment so maybe that is why you are doing some things in a certain way.  At the end of the day, we all take different approaches;  hopefully, this might give you a couple of alternatives.
Derek.