Search options (Page 75 of 104)

Hi David,
Have you tried:
Openfile('myprog.exe','mytext');
That's the way you'd run something like like Notepad when specifying a particular file (see attached), so I'm guessing it might be the same in your case.
Derek.

Hi Again David,
Attached is what I've used in the past to mimic radio buttons.
Rather than have discrete boolean fields for each option, I use a single hidden combobox instead and depending on what radio button image is clicked, set the associated value in the combobox.
The radio buttons images are simply overlaid on top of each other to simulate being clicked on or off.
Maybe this might give you some ideas.
Regards,
Derek.

Hello Marc,
My understanding is that if you use 'copyfile' (for individual files) or 'directorycopy' (for entire directories (and sub-directories)) -
1)   if the destination file or directory doesn't exist, it will be created.
2)   if the destination file of directory already exists, it will, by default, be overwritten.
Please have a look at the attachment (1 example of 'copyfile' and 1 example of 'directorycopy').
I appreciate that these ways of performing back-ups probably won't suit more complex applications, but it does the job for my simple requirements (why buy a ferrari if you only go shopping!).
Hope this helps.
Regards,
Derek.

Hi David, Gonpublc2k,
I thought I'd read somewhere that 'ostype' might work with later versions of Windows;  sorry about that.
However, there's nothing to stop you creating a new system environment variable ('ostype' or whatever you want to call it) and give it the OS Version description.  Then give the script the name of your new environment variable and it's value pulls through to the program like any other environment variable.  But obviously, you'd need to do that for each PC that's running your program (which may be impractical).
Another way might be to write a batch file that runs the DOS command that shows the Operating System details (in XP, the command is 'ver', but I'm not sure about later versions) and then write the output to a file.  Then, in the script, read the contents of that file into your edit field.
I've attached an example (but obviously you'll need to edit the included batch file and replace 'ver' with whatever DOS command works with your version of Windows);  the screenshot shows how it looks on my machine but yours will obviously be different.
At least this might give you a couple of options.
Derek.

Hi Chaoba,
Обычно я добавляю панель в форму, а затем помещаю на нее новые объекты или, если объекты уже существуют в форме, я вырезаю и вставляю их в панель; с помощью этого метода они становятся подчиненными панели, поэтому все, что вы делаете с панелью (например, перемещаете, скрываете, включаете и т. д.), автоматически происходит и со всеми подчиненными объектами. Это может сэкономить много времени.
«Вывести на передний план» и «Отправить на задний план» позволяет размещать объекты поверх панели, но при этом методе они не подчиняются панели и, таким образом, продолжают вести себя независимо.
Почему объекты меток ведут себя по-разному, я не знаю.
Но когда вы привыкаете к дизайнеру форм, я не вижу много вещей, которые вы не можете сделать.
С Уважением,
Derek.

Usually, i add a panel to a form and then place new objects onto it or, if objects already exist on the form, then I cut and paste them onto the panel;  with this method, they become subordinate to the panel, so everything you do to the panel (for example, move, hide, enable etc) automatically happens to all the subordinate objects as well.  This can save a lot of time.
'Bring to front' and 'send to back' allows you to place objects on top of a panel but with this method they are not subordinate to the panel and so still behave independently.
Why label objects behave differently, I do not know.
But when you get used to the form designer, I don't find there are many things that you can't do.

Hi David,
How's things?
I think there are other environment variables that might show more detailed information but perhaps ('OS') is enough for what you need?
Please have a look at the attached (XP probably shows up as _NT - but I guess if you wanted, you could just add another line of script to substitute _XP where it finds _NT).
Derek.

Hi Raheel,
Are you trying it on data that you'd added before you created the relationship?  If so, there wouldn't be any id's in place to link the data.
Can you attach what you've done and maybe I or someone else might spot something?
Derek.

Hello Raheel,
I understand what you're trying to do - load the dbimage into the 'picture' object in Fastreport by script.  But like you, I can't work out what the correct syntax should be.
As a work-around, and because you only ever have 1 row in your 'receipts' table, I would simply create a relationship between your 'database' table and your 'receipt' table, pre-set form1.combobox2 to '1' (using index1) and hide it;  that way,  the logo (and the header and footer messages) can be added as data fields to the dataset that you define for the report in the standard way.
I don't know if that's an acceptable solution for you?
Derek.

Hi Eyeman303,
As a general 'rule of thumb', you should try to not hold the same piece of data more than once in your database;  creating a new field to hold information that you are already holding (firstname, middlename, lastname) introduces data redundancy.  I would suggest using a calculated field instead (please see attached).
I have had a quick look at your project and the database has a number of tables that seem unnecessary (middle_name, last_name, age_years, years, age_months, unit_price, subform2_opd_registration).  Also, some of the relationships do not look correct.
If I have some time, I can go through it and suggest an alternative schema that has no redundancy and is less complex, if this would be of help;  this should also help in reducing the number of forms that you currently have.  One suggestion might be to use 'editable tablegrids' for your 'look-up' forms (salutation, gender, next of kin etc - these can all be done on one form;  your project would load a lot faster with fewer forms.
Derek.

Hi Kees,
I don't know of a tutorial for 'treeview' specifically but have a look at the attached and hopefully it will be enough to give you a overview.
There are a couple of things to remember if you use a 'treeview'.
1.  Your table must have a 'parentid' (defined as integer);  this is how MVD internally links child and parent nodes together on the hierarchy.
2.  Your table should have a 'description' (text) field that contains the legend that appears on the hierarchy.
3.  On your form, the treeview object must be set to 'editable' (see screenshot in the attachment).
4.  You must nominate a form on which you maintain your hierarchy and any other data (again, see screenshot in the attachment).
The attachment has 2 examples.
Keestree1 shows a simple hierarchy with additional fields as cells attached to the same node.
Keestree2 shows the same hierarchy but with the additional fields displayed as edit fields on the form (this way requires a small script).
There are other options but these 2 basic ways should be enough to get you started.
Hope this helps,
Derek.

Привет Agatlogic101,,
Вы можете сделать это так (см. Пример).
С Уважением,
Derek.