|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| − | Hi,
| |
| − | can i say that you had haved 2 real problems ?<br>
| |
| − | first: thers no Suse rpm for Lazarus (the depencies arent right)
| |
| − | :: I think an Suse RPM Package is in work see [[Road To 1.0]]
| |
| − | second: its no help system installed in lazarus
| |
| | | | |
| − | Iam right with this ?
| |
| − |
| |
| − |
| |
| − | 07-03-06, Seekbirdy:
| |
| − |
| |
| − | Hi!
| |
| − | Some words about a topic called '''Change my thinking or don't use SQLdb'''.
| |
| − | Why don't use a 'Data Module' unit for this stuff? Just declare your connection in this unit and include it in every unit/form when you use the connection.
| |
| − |
| |
| − | Suppose you have a data module called DmMain in your project, IBConnection (or PQConnection if you like it more :)) and you want use this connection in some form called Form1. Just add DmMain to 'uses' list of Form1 and then you can refer to the connection as DmMain.IBConnection (or DmMain.PQConnection if you like it more :)).
| |
| − |
| |
| − | I have been using this technique in Delphi for ages, and, since we can see smth called 'Data module' in Lazarus, this should be worked for Lazarus too.
| |
| − | Hope this helps and I've rightly understood the problem.
| |
