Search options (Page 111 of 115)

Good Evening Jumper,
It's 'standard' MVD which is why the script is empty (apart from the "hello world").

Using the example I knocked up, the 2 digit code and the description are fields in a table called 'states';  it is the table that gets populated, NOT the combobox.  The combobox is just a way of letting you pick a value from the 'states' table.  It is not a table itself and doesn't hold any data.
Have a look at the attached screenshot and follow it through.
On Form1 click the 'STATES TABLE' button.  This takes you to Form4 which is a list of rows in the 'states' table that have been added so far. 
Click  the 'ADD STATE' button to create more entries in the 'states' table..
When you have finished, go back to Form1 and click on the 'ADD' button to go to Form3 where you start adding suppliers. 
This is where you see the combobox in action - remember, it is simply a convenient way of presenting you with a pick-list of values held in the 'states' table.
Hope this clears things up a bit and if you need any more help, just shout.
Derek.

Hi Jumper, Mathias,
I've been using www.google.com/maps/place for a while now in an application and it works fine.
In England, we use postcodes that take you straight to specific streets so it is great for cross checking data. 
In the application, I build 2 urls from my address data:
1.  a url using just the postcode which, when clicked, lets me confirm the street and town.
(eg.  www.google.com/maps/place/wv95lj)
2. a url  concatenated from the street and town which, when clicked, shows me the associated postcode.
(eg www.google.com/maps/place/lesscroft+close,+wolverhampton)
While the postcode search is perhaps more relevant to England, the street and town search works world-wide. For example,
www.google.com/maps/place/armitage+close,+red+deer  (in Canada)
www.google.com/maps/place/lynne+place,+longview  (in USA)
www.google.com/maps/place/carrer+san+francisco,+altea  (Spain).
Hope this helps others with similar requirements.
Derek.

Good Evening Tcoton,
I have always been puzzled that the attributes of the objects on the form do not get reset when it is closed.
So I end up ignoring an object's default status and set it explicitly one way or the other which takes more time and makes the script longer, but it's the only way I know to make sure it works 100%.
Sorry - I know it's not what you wanted to hear - LOL!
Derek.

Hi EHWagner, Hi Dmitry,
I was having a look at your problem (which I think is actually more awkward than it initially appears!).
Creating inserts into the parent-copy and child-copy tables is relatively straightforward.  However, I believe Dmitry's example encounters the same two basic problems that I was concerned about.  They are:
1.  DELETIONS - if you delete a parent record and any child records, presumably you want to check if there are any associated parent and child records in the parent-copy and child-copy tables and have them also deleted.  Awkward because both pairs of tables are essentially 'stand-alone' and there is no record-id to relate them, so you are relying on users to also make the same deletions in the copy tables (which they all say they will do but we know they won't !!).
2.  CHANGES - if you change a parent record and any child records, presumably you want to check if there are any associated parent and child records  in the parent-copy and child-copy tables and have them also changed.  Again, awkward.  In Dmitry's example, a change to the parent and / or child record creates an INSERT in the parent copy table.  But to be fair, I think Dmitry's example is only currently intended to perform inserts. 
Taking the two problems together, you could find that, rather than the copies being sub-sets of the original tables, they will quickly start to hold completely different records.
Still, it's an interesting problem and I'm sure there's a way of doing it.  I'll let you know if I come up with anything.
Derek.

Hi TCoton, Mathias,
Yes, it can make the form look unbalanced.
You could replaced the  xxx.visible := false  with xxx.enabled := false.  That might make it look better.
I've attached an example - it might not have all your conditions, but the principle is the same.
Derek.

Good Evening Mathias, Smoustafa, Jean and Dmitry,

@Mathias
It is true that we never know what we don't know - till someone else mentions it!!  Then you think "I wish I'd been aware of that 6 months ago!!"

In case you are interested, I have attached a small project I was working on that does a lot of master / detail work.  This includes doing all of the Adds, Changes, Deletions and Searches just using one form.

The script is messy (!) because users wanted to be able to do as much as possible with keyboard short cuts because it is quicker for them.   So much of the complication is trying to keep focus on the grid, remembering what row you are positioned on etc etc.  If you do not need any of those things and can use the mouse, the script would be quite simple.

Hope it gives you some ideas,

Derek

Hi Smoustafa, Mathmathou, Dmitry,

Normally, you would  use a separate form to show the fields of the record you select in the tablegrid.  But there is nothing to stop you from showing those fields on the same form.

Attached is Mathmathou's example but done without using a script.  (Sorry Mathmathou - I was too lazy to write an example so I stole yours - LOL!).

Hope this helps.

Derek.

Hi Roger,

You only need to disable the file menu options once, on the first form that is called when you run your application.  So, your script would typically read as follows:

procedure Form1_OnShow (Sender: string; Action: string);
begin
  form1.mniAbout.Visible := False;
  form1.mniOptions.Visible := False;
  form1.mniFile.Visible := False;
end;

The menu options on Form1 and any other form are now all removed.

Hope this helps,
Derek

Hello Jumper,
Usually you will get this problem if you have already started to add data to your project in ANY of your tables, not just the table that you are trying to make a field not nullable in.
In the directory where your project files are held, delete the sqlite.db file, go back into your project and you should then be able to make the required field not nullable.  For this reason, it's best to only enter a small amount of test data until you're 100% sure of the structure, conditions etc to avoid having to re-enter stuff.
Hope this helps,
Derek.

Sorry - forgot to add the screenshot!

No problem, and glad it helped.
There's a few of the users who are happy to help out (probably because we've all been there at some stage!) and Dmitry (Mr "My Visual Database") is totally amazing at getting back to you with answers and suggestions to all sorts of questions.
Most of what I've picked up is from downloading other people's projects that were attached to posts in this forum and reading through how they tackled various things and then carrying on from there.
MVD is an excellent tool - hope your evaluation goes well and you decide to stick with it.
Derek.

Hi Again Ehwagner,

Don't know about awesome - just learn a lot from my mistakes along the way!

To get around the problem you have with adding new records and it not showing immediately, it might help if you attach a little bit of code to the 'on after save' button event to update the affected grid (eg - form1.tablegrid1.dbupdate;) - that often does the trick.  I imagine you would also have the same problem if you were deleting a record or amending its Business Type.

I had a bit more time today so I reworked my previous 'rush-job' to include the tablegrid1.dbupdate code and some other bits as well.  It's attached if you want to have a look at it and then chop it about to suit.  I'm sure it's different to how you want it to work in 'real-life' but it might give you some ideas and clues as to how to do certain things in MVD.

Good Luck,

Derek.