Search options (Page 6 of 15)

Papafrankc,

I don't have an answer to your problem but, I think once you have solved the problem your end users will not see this, but each time you compile the program you might have to recheck all your drop down boxes before distributing your program.

As an example my project suffers from two annoyances.

1. A group box and labels keep moving each time I compile the program.
2. My date time pickers like to untick themselves between compilations.

So I have to test to make sure after I have added a new form or script code that these items are reflecting what I want before I recompile.

I suspect your dropdown box problem may well require a similar approach.

Согласно StackOverflow, единственный способ сделать текст в окне сообщения или диалоговом окне сообщения жирным шрифтом - это создать новый класс или создать собственное окно сообщения.

Основные шаги создания такой формы:
1. создать новую форму
2. Добавьте метку и две кнопки
3. Установите для надписи жирный шрифт.
4. добавить обработчик к обеим кнопкам, закрыв форму и установив какое-то свойство, для которого была нажата кнопка.

https://stackoverflow.com/questions/225 … messagebox

According to StackOverflow the only way you can make the text in messagebox or messgedialog bold, is to either create a new class or design your own message box.

The basics steps of creating such a form:
1.Create a new form
2.Add a label and two buttons
3.Set the label font to Bold
4.add handler to both buttons, closing the form and setting some property for which button was pressed.

https://stackoverflow.com/questions/225 … messagebox

Hi Kees,

I think Brian means using a file similar to MVD's 'Settings.ini'.

To load a ini file use code similar to:

procedure loadSettings;
var
  settingsIni : TStringlist;
  lngth : integer;
begin
   settingsIni := TStringList.Create;
   settingsIni.LoadFromFile ('Settings.ini');
   dbName := SettingsIni[4];
   SettingsIni.free;
   lngth := Length(dbName) - 7;
   dbName := copy(dbName, 8, lngth);
   FrmMain.lbDbPath.Caption := ExtractFilePath(Application.ExeName)+ dbName;
end;

That code is for loading the standard settings.ini file and finding the name of the database.

To save a file change LoadFromFile to SaveToFile .

Papafrankc

JB is the man to ask as that is his code snippet.

I'd be wary about saving the serial numbers to a table unless you can encode them (which is possible) as otherwise anyone with copy of SQL Browser or SQL Studio would be able to open the database, read and take your keys.

To save the key to registry all you need is to write:

reg.WriteString('Key', 'sKey');

Assuming that sKey now contains the serial entered via your textbox.

Papafrankc,

I think this needs to be a global constant, so will need to be at the top of the script file, before any procedure or functions.

You can either write:
CONST
   APP_NAME = 'records.exe';

and then in the function   APP_NAME

or

CONST
   APP_NAME = records.exe;

in the nag screen function  'APP_NAME' either should work.

If you copied and pasted JB's code, you might have missed changing some of Jean's frmNagScreen to the name of your own 'nag' forms' name.

PS. Sorry JB I didn't see your reply when I was typing mine.

A possible but unsatisfactory workaround is to use a try.... except wrap-around.

try
      Outlook := CreateOleObject('Outlook.Application');



    vMailItem := Outlook.GetNamespace('MAPI');

    vMailItem.Logon;
    vMailItem := Outlook.CreateItem(olMailItem);
    vMailItem.Recipients.Add('dibbledabble@somewhere.someplace');
    vMailItem.Subject := 'What a wonderful test email';
    vMailItem.Body := 'This is a test --> how amazing';
    vMailItem.Send;
    Outlook := nil;
    except
     openFile('mailto:?Subject=PURCHASE ORDER PO: 123 &Body= no outlook installed')
 end;

Hi dbk,

First I should note that using the above code you never see your email message, by that I mean the email is created and sent 'behind the scenes', unlike using mailto: or openfile(mailto:) which opens the email create page.

I don't know the answer to the rest of your question. I do know that the Outlook object has a number of item folders that can be searched such as contacts, calendar, email folders.

This link to Microsoft might help https://docs.microsoft.com/en-us/previo … office.11)

or

http://delphi-kb.blogspot.com/2011/06/o … _6280.html

Would this help?

Ignore the SQL, you don't need to do that, the trick is in using MessageDlg function which has both button options and a message capability.

procedure frmEditOrderQty_btnFrmAmendDeleteRecord_OnClick (Sender: TObject; var Cancel: boolean);
 var
 text : string;
 btn :integer;
begin

  
   text := 'ORDER ITEM '+#13#13 + frmEditOrderQty.edtfrmAmendDescription.Text +'  x '+ frmEditOrderQty.edtNewQty.Text;

   btn := messageDlg('CONFIRM DELETION OF '+text,mtWarning, mbCancel+mbOK, 0);

   if  btn  = mrCancel then
      Exit
   else
     begin
       SQLExecute('DELETE FROM orders WHERE orders.id =  "'+ intToStr(frmMain.tgOrders.dbItemID) +'"');
       ShowMessage(#13#13 + text + ' has been DELETED' );
       frmMain.tgOrders.dbupdate
      end;

 // frmEditOrderQty.Enabled := True;

  frmEditOrderQty.Close;

end;

For other MessageDlg options see http://www.delphibasics.co.uk/RTL.asp?Name=messagedlg

Hi Jean,

Are you sure about that?  Under the menu item 'Project' there is the Webgrid option, which makes for a very basic web based program. It requires mySql as the database.

A link to a demonstration page  http://myvisualdatabase.com/webgrid_rus/

vit007

You used Form1.TableGrid1.CELL[0,i], the example code used Form1.TableGrid1.CELLS[0,i] - important difference.

Вы использовали Form1.TableGrid1.CELL[0, i], в примере кода использовалась Form1.TableGrid1. CELLS[0, i] - важное отличие.