Search options (Page 25 of 25)

Derek,
Your example is definitely an efficient way to consolidate comboboxes. I've done that with other software products. Your method is certainly the way to go in your specific project and would stick with it.

Ok. Thank you Dinitry.

Jean - I totally agree, all apps should be designed and built to suit the needs of the end user and their workflow. It's got to be as easy and simple as possible. Most Windows programs probably could be built without any kind of menubar. There's really no right or wrong way. I guess the right way is what the end user actually requires. Most users of Windows programs come to expect some sort of menubar and maybe Roger's user(s) is one of them. Maybe Roger can show them an alternative. Based on what I have learned from Dimitry's example, it could get quite involved building menubars throughout the app especially if there are a lot of forms. I agree it can be disruptive to bounce around forms by placing all your forms in a menubar of all the other forms. Not knowing Roger's user requirements, this forum can only try to help him get to where he needs to be if possible.

Derek - It's funny you mentioned a "false" form. That's exactly what I did in my project while testing MVD. Most Windows applications have a main application window from which dialog boxes, forms, reports, etc are displayed within. I noticed very early on in evaluating MVD that this is not the case with MVD. All forms which are not maximized open up over your desktop or whatever program is running behind the MVD form. So I created as my first form a backdrop window (maximized). From there you can go to a login form or whatever is the real first app form through a script, not a button. Essentially all forms from that point on look to be opened within the main window. It works and it looks more professional. I know this is off topic from the menus, but I thought I would mention it to you since you said "(can't imagine why though)"  :-)

Derek,
At this point I'm only evaluating MVD. During the trial period I'm just building a rudimentary system to make sure I can do everything the design calls for. So far the software seems pretty strong.  I've been able to do most everything. The only drawback I see in the software so far is that too many properties need to be set using scripts. All properties should be done on the component design and scripts should only be needed to override those properties during run time. I understand that the new beta version has more properties which may take care of my issue. I have not tried it during the trial. I didn't want to mix my testing and evaluation on a beta version. The only other thing that bothers me is that the documentation is weak. The new help system is a huge step in the right direction. I believe it can be improved upon by defining ALL the functions available in MVD, ie String manipulations, date functions, etc, etc. I tried using things from Delphi Basics, but apparently there are discrepancies between Delphi and MVD. I'm definitely not a Pascal expert, but I've learned other languages fairly easily in the past if I have a good reference manual. I've learned some things from this forum, but if Dimitry ever got hit by a beer truck we might be in trouble. And it sounds like he is the author and developer of MVD. That scares me if something happened to him or he decides not to keep the software up-to-date any longer. Other than that, I think the software is pretty decent and easy to use.

Thank you Dimitry. That clears it up. I appreciate your quick response.

Tcoton question: single record means one table row.

Derek:
Question 1: Just occasionally (yes a manual request on a form button). Second parent will not have the same number of rows.

Question 2: Yes this is true for the child tables. And yes your scenario is correct. Don't always want a parent row copied, but when I do I always want the child records to be copied.

Question 3: Yes

Yes you are both correct. It's definitely not complicated in theory. I just don't know how to structure it in an SQL statement. The parent copy I'm sure can be done using an Insert....select type statement, but bringing over the child records and assigning them to the newly inserted parent record is my hang-up.
.

Thank you Dimitry. Maybe changing header fonts and size can be a feature in a new release.  And maybe column wordwrap can be more or less a property in a future release, to reduce coding in scripts. But at least there is a solution right now for it.  Thanks again for your response.

Perfect, Derek. I adapted what you did into my project and it works beautifully. Thank you so much for your help. I really do appreciate it. It's good to know that the support on here is dependable especially as I am testing and evaluating this software.

You're awesome Derek. I got it working using your concept. Since I don't have a seller tablegrid on the Seller form, I couldn't use your incremental search feature. However I used your button concept to do an auto search on the Seller form by placing the script function for clicking the button on the form OnShow event as well as the Business_Type combobox change event. It works perfectly (almost - lol).  Although it's not really a show stopper, here is the only time it does not work properly. If I have a buyer who has a Business_Type of let's say "Auto Repair" and I don't have any sellers currently with "Auto Repair" Business_Type, but in the future I have one and add the new seller on the Seller form. When I select "Auto Repair" for the Business_Type for the new seller, I expect the buyers with "Auto Repair" to show in the grid, but it shows an empty grid. However, after saving the Seller record and then go back into the form, the buyers with "Auto Repair" do show up as they are suppose to. I can also change the Business_Type in the combobox and the correct buyers show.  So I know the button search is working but not when a new seller is put in as the first time seller with the same Business_Type as an established buyer(s). Like I said, I could probably live with it. Just wondering if there's a way to get it to work in that situation.

I've learned a lot just from your example Derek. I learned about the Incremental search feature for a button and that apparently search results override Tablegrid settings for what's displayed in the grid box. Bear with me, I'm trying to get a handle on this software. Thanks again Derek.