Search options (Page 59 of 101)

Здравствуй Vickus,
Возможно, сделайте это так.
Derek.

Это маленький скрипт:
процедура Form1_TableGrid1_OnClick (Отправитель: TObject);
начать
   form1.button7.click;
конец;
Выполняется второй инкрементальный поиск (первый инкрементальный поиск автоматически выполняется свойством объекта инкрементного поиска form1.tablegrid1).
Derek.

Здравствуй Tefix,
Если вы хотите заменить «0» на «Нет» и «1» на «Да» как часть вашего SQL-запроса, взгляните на «screenshot1.jpg».
Если он не является частью вашего sql-запроса, я бы использовал вычисляемое поле (синтаксис тот же).
Я думаю, что выравнивание верхних колонтитулов таблицы, столбцов, нижних колонтитулов и т. Д. Является частью свойств объекта tablegrid из Версии 5, но оно не работает с выводом из SQL-запроса, поэтому вам придется написать небольшой скрипт (см. Screenshot2.jpg). Повторите это для столько столбцов, сколько у вас в таблице (номера столбцов начинаются с 0).
С Уважением,
Derek.
.
If you want to replace '0' with 'No' and '1' with 'Yes' as part of your sql query, have a look at 'screenshot1.jpg'.
If it is not part of your sql query, then I would use a caculated field (the syntax is the same).
Aligning tablegrid headers, column, footers etc is part of the tablegrid object properties from Version 5 I think, but it does not work with output from an sql query, so you would have to write a small script (see 'screenshot2.jpg).  Repeat it for as many columns as you have in your tablegrid (column numbers start at 0).

Hi Wood,
I had the same problem a couple of years ago. 
The only solution I could come up with was using panels and setting them to 'enabled = true' or 'enabled = false'. 
You then use 'tab' to go from one field to the next within a block or (in the attached example) use ''left arrow' and 'right arrow'' to jump between blocks (you could use other keys but 'left arrow' and 'right arrow' seemed a logical choice).
I appreciate it's a work-around but perhaps it gives you some ideas,
Derek.

Здравствуй Vdovin,
Отношения между таблицами в порядке, вам просто нужно добавить кнопку поиска (в моем примере этот «поиск» выполняется автоматически).
Пожалуйста, спросите, что-нибудь не понятно.
Derek
(с гугл переводчиком)

Hi Wood,
I understand why you might think that the integer fields are the problem, but I've been able to print a record that has, for example, a value in the RAM field, so I think it might be another issue.
When you change some of your data and try to print, the error message changes and highlights different fields / values so I'm wondering if it might even be the size of the actual select statement (you have 36 components plus their values!) that is causing errors in the query plan - but it's just a guess;  maybe someone else could either confirm or correct me on that.
But you don't actually need to specify any components in your search anyway because you have already selected a single record from the tablegrid on the previous form.  So as a simple fix, I'd suggest you remove them all (see attached screenshot) and run the report like that.
Derek.

Hello Henri,
Please have a look at the attachment for one way of doing it but there are probably other (better!) ways (just couldn't think of any!).
Hope this helps,
Derek.

Здравствуй Maksim,
Вы не можете клонировать форму, но вы можете скопировать любое количество (или все) объектов из одной формы в другую.
Чтобы скопировать один объект, щелкните правой кнопкой мыши, выберите «Copy» и вставьте в новую форму.
Чтобы скопировать несколько объектов, нажмите «Shift», затем щелкните правой кнопкой мыши, выберите «Copy» и вставьте в новую форму.
Derek.

Hello,
OPD_ID is auto-incremented whenever AA_Form_007_OPD_VISIT_REC is opened.  But if you don't close AA_Form_007_OPD_VISIT_REC once the record has been saved, then OPD_ID can't auto-increment until the next time AA_Form_007_OPD_VISIT_REC is opened (see screenshot3)..
As a general rule (just my personal preference), I would always try to close any form once the data has been saved because it's too easy to accidently create duplicate records, blank records etc.  You could always check for this happening (by script) but it's extra work and not playing to MVD's strengths.
When you get 'foreign key constraint failed' error messages, it's because you have data in other tables that is dependent on the row of data you're trying to delete (if it's allowed to happen, you get an 'orphan record'  - ie it's 'parent' no longer exists, and the integrity of a relational database is compromised).
In your case, I imagine you're trying to delete a record from AA_002_REC_Visits but there are still related records in AA_003_REC_Chief_Complaints.  What you need to do is note the ID of the AA_002_REC_Visits record that you can't delete and then find the record(s) in AA_003_REC_Chief_Complaints where the foreign key (ID_AA_002_REC_Visits) is equal to the ID that you've noted. 
Delete all of the relevant rows in AA_003_REC_Chief_Complaints and then go back to AA_002_REC_Visits and the deletion should now work.
Derek.

Hello,
Your application doesn't close completely because the login form is only hidden (AA_Form_001_LOGIN.hide - see line 71 in the script).
The easiest fix is to create an 'on close' event for AA_Form_002_SELECT_MODULE and insert the instruction  AA_Form_001_LOGIN.close;  in the script (see attached screenshot). 
So now, when AA_Form_002_SELECT_MODULE closes, it automatically closes AA_Form_001_LOGIN at the same time;
Derek.

Hi,
It's hard to work out exactly what's going on although it does sound like one of the keys is either not being passed through or not being saved.
Can you attach the latest version of your project and I'll try and have a look.
Derek.

Hi,
Yes, you've got it.
Derek.