Search options (Page 109 of 112)

Hello EHWagner,

I found your problem far more interesting that what I'm supposed to be doing right now - LOL!  So......a couple of questions.

1.  Will the second parent table ALWAYS be populated (so it can be automatic) or just occasionally (so it would be a manual request)? 
In other words, if the first parent table has 1000 rows, will the second parent table also have 1000 rows or only a subset?
2.  Will this also be true between the first and second child tables?
The reason for the questions is that I can see a scenario where you don't always want the parent record to be copied but when you DO copy a parent record, you would ALWAYS want the child record(s) to be copied.
3.  Is this mainly to avoid having to enter data twice? 

I've mocked up a couple of quick solutions but would just like to know the answers to 1. 2. and 3. above before I see which is most suitable.

More generally, I'm intrigued as to why you need to create the additional parent / child tables in the first place.

Derek.

Good Morning TCoton, Mathias,

If I understand your problem correctly, yes, I would do it exactly the same way as Mathias suggests.

Derek.

Sorry - the attachment didn't upload!!  Here it is.

Hi Roger,
I think the problem could simply be the sequence in which your forms are held.
I downloaded your project and encountered the same problem as you. 
When I switched the sequence of the forms, the error is corrected (see roger.jpg).
Maybe this helps.
Derek

Hi Jumper,
Yes, my understanding is that you have to use the 'edit' icon and then the 'additional' option - you can't simply insert a tick on the first 'database tables' screen (even though it looks like it you can).
Notwithstanding that, you would still hit your original problem if you'd already started adding data to any of the tables.
Derek.

Hi Krokodil_sk, Hi Dmitry,
I am not sure if I understand your issue correctly but you can select multiple textboxes, comboboxes, grids etc to move at the same time by holding down ALT and SHIFT.  It makes designing your forms much quicker.
However, (for me) this only works if you move them using the mouse;  if you try to move them using the arrow keys, it only moves the first entity you selected on the form, not all of them.
Hope this helps,
Derek.

Good Morning Dmitry, Ehwagner,
I've wanted to do something similar before - the only way I could think was to remove the column headings in the grid completely and replace them with labels - then you can use whatever size, colour, font etc you want (or mix them!) (see attached screen shot).
But it's not really a solution - more of a work-around - and of course, if a User resizes the column widths, it messes things up.
Derek.

Hi,
Please find attached a rough and ready version of the 'sellercrud' form with a buyers grid attached. 
You need to be careful when you scroll through the various buyers in the sellercrud.tablegrid1 because you are actually in 'amend' mode and will change the business type for the particular seller that has been pulled through onto the 'sellercrud' form.
For that reason, I would probably just use the 'match' form instead - it shows exactly the same information as the 'sellercrud' but without that risk.  I've deliberately left the buyercrud as it was before so you can compare the two different approaches.
Hope it helps,
Derek.

HI Ehwagner,
Once you've set up a 'SEARCH' button, you have a choice of either 'clicking' it or of having it fire automatically. 
In the knock-up example I did, to fire it automatically, you use the 'incremental search property of the search grid to associate it with BUTTON1 (obviously, you don't have to hide the button but it just makes it look neater) - see attached.
It was quickest (I'm lazy!) to show you using the SELLANDBUY form but the principle is exactly the same if you want to put the buyer grid on the SELLER form instead as you suggest.
Glad it helped.
Derek.

Hello Dmitry,
I have tried both your solutions and they work well.
I prefer your idea of putting the SQLQuery code into the script so that all of the grid formatting is properly maintained - looks much better.
As always, thank you for your help.
Have a good day,
Derek.

Hi,
I am not sure if you have a need to store the cars you 'buy' and the cars you 'sell' in 2 separate tables with all the extra problems that might cause.
You could use just 1 table with extra fields to hold additional information about the 'sold price', 'sold date' etc.
Then all you need is 2 grids with filters - one grid automatically shows cars that haven't been sold (for example, with a 'sold price = 0.00) and the other grid automatically shows cars that have been sold (sold price > 0.00).
I have attached a little example of how I might do it if it helps.
Derek.

Hi TCOTON,
I thought that when I first had the problem so tried it with just 2 conditions but it still didn't work.
And then I left outer joined instead - and still it didn't like it!  There is something wrong somewhere but I can't find it!
The only way I have got it to work is by using separate search fields for each column in the grid rather than using an SQLQUERY;  if I can't fix it, I may end up doing that on all the other columns as well, but it isn't quite the way I wanted it to be done.
Thanks again for your interest.
Derek.