Hi Frank,
yeah why not, I'm not saying I won't look at that...
see my parallel to sewer system thou ;)
(I don't need to know how pipes are made or how deep
they are buried, but need to know where the manholes
and sink holes are in case it rains and they be about
to burst up...)
(By the way : sor
On 20 September 2011 16:20, Graeme Geldenhuys wrote:
> On 20/09/2011 16:53, Lukasz Sokol wrote:
> >
> > Thing is - I may not need to know how the sewers work, that they need
> > to be laid with some sort of descent ;) or that you should not use
>
> Then buy a old Delphi 7 (where you still get prin
On 20/09/2011 16:21, Lukasz Sokol wrote:
> On 20/09/2011 16:11, Joost van der Sluis wrote:
>
[...]
>> IIRC, this has been solved in fpc 2.4.4.
>>
>> Joost
>
> OK, one more reason to upgrade... :)
>
> But then, after that it is enough that I ODBCConnection1.Close just, yes ?
For the record - it
On 20/09/2011 16:20, Graeme Geldenhuys wrote:
> On 20/09/2011 16:53, Lukasz Sokol wrote:
>>
>> Thing is - I may not need to know how the sewers work, that they need
>> to be laid with some sort of descent ;) or that you should not use
>
> Then buy a old Delphi 7 (where you still get printed manua
On 20/09/2011 16:11, Joost van der Sluis wrote:
>> So I can actually point to the MDB file I want to look into, but
>> then, when I close it (using the SQLQuery.Close part of the above),
>> and then try to open it again (using the first part again) I get a
>> 'External: SIGSEGV' at the SQLQuery1
On 20/09/2011 16:53, Lukasz Sokol wrote:
>
> Thing is - I may not need to know how the sewers work, that they need
> to be laid with some sort of descent ;) or that you should not use
Then buy a old Delphi 7 (where you still get printed manuals in the box)
and read them from cover to cover.
Reg
On 20/09/2011 16:13, Graeme Geldenhuys wrote:
> On 20/09/2011 14:53, Lukasz Sokol wrote:
>
>> this may not be entirely on-topic to this list, apologies for that;
>
>
> Hmm... I can not help you with your problem, but maybe you could
> take a look at a better design of your code and split your GU
On 20/09/2011 14:53, Lukasz Sokol wrote:
> this may not be entirely on-topic to this list, apologies for that;
Hmm... I can not help you with your problem, but maybe you could
take a look at a better design of your code and split your GUI-code from
the actual work. Google for
[Joost never
On Tue, 2011-09-20 at 13:53 +0100, Lukasz Sokol wrote:
> Hi,
> this may not be entirely on-topic to this list, apologies for that;
> (But since I am (currently) using Lazarus 0.9.28.2 r22279 FPC 2.2.4,
> (and planning to upgrade to latest stable 0.9.30/2.4.something /windows/
> installer distribut
On Tue, 2011-09-20 at 15:42 +0200, Graeme Geldenhuys wrote:
> On 20/09/2011 14:53, Lukasz Sokol wrote:
> > procedure TForm1.Button1Click(Sender: TObject);
> > begin
> > if Label1.Caption = 'ODBC Disconnected' then
> > if OpenDialog1.Execute then
> > begin
> >
> > ODBCConnection
I knew I could count on Graeme for an answer (and a plug ;)
On 20/09/2011 14:42, Graeme Geldenhuys wrote:
[snip]
>
> Maybe we should stop you right there, and teach you the "correct"
> OOP way of doing database programming. :) No GUI unit should contain
> code as listed above...
That was just a
On 20/09/2011 14:53, Lukasz Sokol wrote:
> procedure TForm1.Button1Click(Sender: TObject);
> begin
> if Label1.Caption = 'ODBC Disconnected' then
> if OpenDialog1.Execute then
> begin
>
> ODBCConnection1.Params.Add('DBQ='+OpenDialog1.FileName);
>// ODBCConnection1.Open;
Hi,
this may not be entirely on-topic to this list, apologies for that;
(But since I am (currently) using Lazarus 0.9.28.2 r22279 FPC 2.2.4,
(and planning to upgrade to latest stable 0.9.30/2.4.something /windows/
installer distribution),
the offtopic is somehow diminished)
I looked up http://wik
13 matches
Mail list logo
