Search options (Page 3 of 109)

Uploading your project is also very helpful in trying to understand your requirement (delete the '.exe' file and then zip the project folder).
Derek.

Hi Sparrow,
Yes, I see the problem now.
I'll have a look later on and see if it can be fixed.
Thanks,
Derek.

Hi Igor, Sparrow,
Attached is an example of a ''treeview'' with functionality to move nodes (including children) by drag and drop (click and hold down the mouse on the node you want to move, drag it to its new position and then release the mouse).
I think Jean and Adam use ''treeviews'' quite a lot so maybe they (and others) will find this useful.
Derek.

Привет SNKip, Sparrow,
В приложении приведен пример, где вы создаете новую подпапку для каждой фотографии (имя подпапки — это идентификатор записи).
Возможно, это поможет.
Derek
.
Attached is an example where you create a new sub-folder for every photo (the name of the sub-folder is the ID of the record).

Hi,
It's all subjective but personally, I think MVD is one of the simpler and yet still powerful programs for writing and distributing your own applications.
However, no matter which product you choose, all of them require a basic understanding of database design and what a relational database is.   What it is NOT is a spreadsheet yet all too often we see database design that tries to replicate a flat file structure and unsurprisingly fails.
From the outline of your requirement, it is something that can be done using MVD but I would advise against 'trying to run before you can walk'.  Too many people try to 'climb Mount Everest' with their very first project, get understandably disillusioned when they encounter problems and then give up.
Also be prepared to change the way you currently operate so that you can take full advantage of how MVD (or any other product) works.
Regards,
Derek.

Привет Oleg,
Забыл сказать, что это можно сделать и без скрипта - посмотрите прикрепленный скриншот.
Derek.

Привет Delphinsl,
Не уверен, что правильно понимаю ваш вопрос, но думаю, что это необходимый вам синтаксис.

procedure Form1_TableGrid1_OnCellClick (Sender: TObject; ACol, ARow: Integer);
begin
  if Form1.TableGrid1.cell[0,arow].AsBoolean = false then ........ etc etc.
end;

Также смотрите прикрепленный пример.
С уважением
Derek.

Hi Igor,
Attached is a fix for the problem with default values not appearing in 'rabat' and 'PDV' (see in the script).
However, I've had a look at your project and I think there are basic design issues that you should consider before you develop your project any further.
A couple of things that I noticed (there are others);
1.  you have an 'operaters' table - does this mean that your project will be used by more than a couple of people at the same time?  You might want to consider using MYSQL rather than SQLite as your database (although if concurrency is not a major concern, you should be okay to stick with SQLite as your database).
2.  You have set up a relationship between the 'usluge' and 'stavke' tables in your data schema;  however, because of the way you have designed your forms (specifically 'formusluge'), this relationship is not being populated.
3.  There is a lot of duplication of fields in the 'usluge' and 'stavke' tables.  This may be intentional if you are using the information in 'usluge' as defaults but then want to change some of those defaults before populating the 'stavke' table.  But having fields (for example 'kolicina') in the 'usluge' table doesn't make any sense (unless you are also wanting to use it to monitor stock levels etc).  Another example is 'artikel' that appears in both tables - surely 'artikel' (and 'jedinicnaMjera') would be common to both 'usluge' and 'stavke'  tables otherwise why have a relationship between them in the first place.
4.  I understand that different items in the 'usluge' table can have different 'PDV' rates but would you have a different  'PDV' rate on the 'slavke' table for the same item?
5.  You need to re-do 'formusluge' - maintaining 'usluge' data and 'stavke' data not only on the same form but also using the same fields(!) is going to cause you a lot of problems.  Using a separate form for 'usluge' data will both simplify and fix a few problems.
6.  You have a 'napomena' field in the 'nalozi' table but this is not related to the 'napomena' table which doesn't seem to do anything.
7   Consider using 'editable tablegrids' for your 'look up' reference data (it gives your project a clearer structure, reduces the number of forms and is a lot quicker to write).  The 'kupci', 'operater', 'mjeseci', 'godina' and 'usluge' tables could all be managed this way.
As a general observation, your database design looks a bit as if you are using a 'relational database' (ie SQLite) in a non-relational way (we often see this when someone tries to replicate something that was previously done in a spreadsheet and while it can be done, it doesn't take full advantage of what a relational database can offer).
I appreciate that your project is still being worked on and some of the outstanding issues may be known to you.  But I'd strongly advise sorting out the above points before making any further progress.
Do not take any of the above points as critisisms;  trying to design quite a complicated requirement as your first MVD project is not easy and a lot of what you've managed so far is working okay.
Regards,
Derek.

Hi Igor,
If you still want to use the record_counter functionality, you can just copy it to an edit field and then you can make any adjustments that you want.
And there are quite few different ways to achieve this.
One suggestion is in the enclosed attachment.
1.  You do not have to use the record counter at all - just type in an invoice number in whatever format you want.
2.  If you want to use the record counter, enter '=' in the 'Invoice No' field.
3.  If you want to include the record counter as part of the invoice no', enter '=' in the 'Invoice No' field and then make any additional adjustments manually.
It really doesn't matter which method you choose but it's important, once you've decided, to be consistent so I'd make changes at that stage so that the program forces that consistency.
Regards,
Derek.

Hi,
See the attached example (Option 1).
Is there a reason why you can't use a 'counter' filed type - this will automatically add 1 to the order number every time without you having to write any script (Option 2).
Also in Option 2, instead of placing the order number in an edit field (if the user is unable to do anything with it, then why have it there simply taking up space?), the order number is displayed as part of the form's header caption).
Derek.

Hi Adam, Sparrow,
Had a bit of time so smarted up the script to remove all of the ''repeats'' and also do away with frmitems.edit2 (which was being used to temporarily hold the hex color value);  now it just applies it directly to each of the frmitems.edcolor fields.
Anything not clear, just shout

Hi,
Try it like this

procedure Form1_TableGrid1_OnChange (Sender: TObject);
begin
  form1.edit1.text := form1.tablegrid1.Columns[2].Footer.caption;
end;

See it working in the attachment.
Derek.