Hi Alexandre, (all others please feel free to comment too)
In my application, in the many forms it consist of, I use a number of data manipulation functions. Like a functions to return a part of a string after a certain character in the string, or special formatting routines and so on. All small functions that only manipulates what they get, and never hold onto any data.
Over time I have built up quite a collection of functions, and with the ease of adding such a "toolbox" unit to the uses clause, and having all them functions available in the code, I must admit i have being holding on to a lot of those, instead of using the newer Windows equivalents. I have adapted many to use newer windows standards, but still keep the ease of having a function at hand, instead of writing it the windows way directly in code, every time it needed.
Some of these functions I also use in my IW application, and I have added such a unit to the uses clause of a number of the forms in the application.
My question regarding safe vars in this context is: Since these units are formless, and as such not created specifically by the form, how safe are they then ?
And if they are not safe, how do I make them safe ?
I do not want to add every one of the functions I use to the Form Class def. in every form where it is used, if I can avoid it, but will of course if I have to. In that case it would likely be as an .inc file and compiler directive.
I have attached a small example to maybe better understand what I'm referring to, though I'm pretty sure you know very well what I'm talking about.
The attached file should have been LFunks.pas but the extension was not allowed as attachment, so I renamed it LFunks.txt.
I need the functionality of an editable combobox, meaning a control which is loaded with predefined values, but which also allows the user to enter a value not in the list, as if it was a normal IwEdit control. Like Delphi's Drop-Down combobox.
The IwCombobox do not seem to allow that and, at least as far as I know, setting the editable property do not change that.
What is it I'm missing ?
Or do any of you have good proposals of how to accomplish this behavior in another way ?
This is for you, but everybody else please feel free to comment as well:
You once recommended I put the DBConnection in the UserSession, and then created a datamodule for every form I make, where DB related components should be placed. For me, as you probably all know by now, the DB related components I use is an ADO DBConnection in UserSession, and ADO the components are ADOQuery and ADOStoredproc, in the datamodules.
With my newfound knowledge of how and where to put variables, coming from other users comment on this forum (thanks to all) and going through a lot on threads in this forum, a lot of documentation on your homepage, a lot of googled information, and some of the older IW forum entries on then Embarcadero site. During all the reading I believe I am certain that ANY form I create at runtime, and any procedure and function I use, and any variable, local for a form or global in UserSession, is safe form interference from other sessions, provided everything is defined within the limits of the Form Class. That is, from Private / Public down to the END definition for the class. Local vars and procedure / function definitions are no go !!
Can you confirm that that is a correct assumption ?
Also, that the datamodule I need for a form, is included in the forms uses list, defined as dm:= {moduleclassname}; in the private section of the form class, and created in the forms create event with dm := {datamoduleclassname}.create(self); I take it that that is correct as well ?, though I do understand there are room for differences like that the datamodule do NOT HAVETO be created in the forms oncreate event, as long as it is created before it's needed, and that it can have any name, not necessarily "dm".
Finally, I have come to learn, and I am not sure you did not already tell me that long time ago, that it is vital that settings for the ADO components connection property is done in the datamodule at runtime, like in the DataModule OnCreate event, and not at design time. Other users have mentioned that as well (again thanks to you).
And that is all there is too it, I believe. Can you confirm that ?
I know ADO are not thread safe, and if I created threads within my form, I should handle threads and make them safe, but also that as long as I do not create threads, it is not necessary. The Session, and among that the ADO components, is shielded from access from other sessions.
Is there anything else I should be aware of, that you (or any of you reading this) can think of ?
I thank you a lot for the information you cave me a long time ago (9 months) and I just wish I could have remembered it all. It would have saved me from a lot of anger and extra work. But such is life. What does not kill you makes you stronger, and what you learn by trial and error, is easier remembered than written words.
I am testing IW with "http.sys" as a server, and for this, I converted an Indy IW server functional application to 'http.sys' according to this page. The application compiles ok, I set it to run as administrative local, it shows up normally, but when I open a web page with any browser in the application page it loads nothing and after a few seconds it freezes Windows 10 completely. After a while, it goes to Windows 10 blue screen and shows as stopping code "DPC_WATCHDOG_VIOLATION".
I thought it could be something not properly set in my application, so I try running the 'HttpSysDemo' application too, but it behaves the same way, freezing the computer after a few seconds.
I tried disabling the antivirus too but to no avail. I tried the conversion using the latest IW version.
To start off, I know nothing about SSL or TLS. We have a couple of clients that have requested to add SSL to our Webserver app. The clients are providing access to documents for their customers and will have no control over browser usage.
I am using XE7, IW 14.2.12 and I am trying to run the StandAloneSSL demo.
Downloaded the OpenSSL dll's 1.02q and placed them in the folder with the freshly compiled StandAloneSSL.exe.
With all browsers I am getting the error, this test was with Firefox :
Error code: SSL_ERROR_UNSUPPORTED_VERSION
This website might not support the TLS 1.2 protocol, which is the minimum version supported by Firefox. Enabling TLS 1.0 and TLS 1.1 might allow this connection to succeed.
TLS 1.0 and TLS 1.1 will be permanently disabled in a future release.
The question is what should I assign to the CipherList and or SSLVersions?
I have a multiform application, created as a SA HTTP.SYS EXE-file, placed on a SQL server where it runs as a Service. The username to start the service has been granted Logon as Service, and the same user has been granted logon to the database. Thereby the program can access and manipulate data in the SQL database. All good.
My program is created with UniqueUrl = on. It seem to be working as all UserSession vars for each user seem to be ok and intact individually. All good as well.
The program uses ADOConnection and ADOQuery, or ADOStoredProc to access and manipulate data in the various tables in my database.
Now it turns out there is multiuser problem. When calling a select from the same table from 2 different users and program instances, it appears that User 1 receives the rows User 2 selected. I have a search form showing a number of records depending on individual search criteria, and it appears as if results are being mixed among the users.
Where the IW application itself appears to be multiuser (thread?) safe, the ADOconnection do not.
Is that a well know problem with a well known solution or is this news for everyone ?
As it is the same username performing the call (the Logon as Service username) could it simply be a SQL problem ?
I'm fishing a bit here as I don't really know what to do, so if anyone have any proposals I will be very grateful to hear them.
I am using Rad Studio Tokyo 10.2.3 with Intraweb 14.2.7
How to use IWDBGRid CurrentField property to access the content of the current cell.
For example if the current cell contains a text: IWDBGrid1->CurrentField->AsWideString generates an access violation error
