> So if something is OLE DB capable then it is apparently a short step from there
> to ADO which of course means the BDE is bypassed.
>
OLE DB = driver for ADO.
ADO-MD = multi dimensional ADO, ie OLAP, which is rather cool...
N
--
Nic Wise - +64.21.676.418 - +64.9.277.5309 - [EMAIL PROTECTED]
For all of MS's faults, ADO is quite a nice interface, and if you just
want a result set to cycle thru (ie, while not eof to next),
its REALLY easy and quite powerfull. If you want data aware controls,
you need something that Delphi and its data aware controls will talk to
- hence ADOExpress.
N
Just be warned that when you change a packages, you really need to
recompile both the package *and* the application that uses the package.
This may, or may not, become a pain in the butt for you.
Kerry S
--- Myles Penlington <[EMAIL PROTECTED]> wrote:
> Is this one? of the reasons Borland inven
HI all.
I am wanting to do the following.
I have a server that I will send an HTTP request to on a specific port, i.e.
http://127.0.0.1:/
When this happens, I want to pass back some HTTP Headers and some HTML code
(prob. just hello at this stage).
Now I have written a wee server that works,
DPL is the D3 name for BPL (which is D4/C++ Builder).
DPK is the source code extension, just like DCP is the complied package -
collection of DCU's, but you distribute the runtime BPL/DPL files.
> -Original Message-
> From: Carl Reynolds [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, Septembe
Good points! I replaced my DLL with a runtime package and the program
now works (I can place the BPL form on a TabSheet). Well, based on that
I would strongly advocate using packages instead of DLLs where the VCL
is involved.
BTW, did you mean DPK/BPL, or is a DPL something new (and exciting :)
Is this one? of the reasons Borland invented the DPL/BPL libraries which is
a superset of the DLL for Delphi use??
And perhaps we should be using the DPL/BPL instead (and hence get around
these kind of problems)?
Myles.
> -Original Message-
> From: Carl Reynolds [SMTP:[EMAIL PROTECTED]]
Yeah, if I remove ShareMem from my uses clauses, funnily enough my test
program doesn't work anymore either - with the same problem as first
mentioned! Rohit, I'm presuming you don't need a copy of it anymore.
My guess is if there are any TStringFields, which use long strings, in
your table data
> Aaarrgghh, when did they add the rest of the to the help. It wasnt
> there last time I read it probably in D2.
They had to put something in to replace the huge piles that they took out
(like a code example of nearly every property for nearly every component in
delphi 1)... The help has to be
Aaarrgghh, when did they add the rest of the to the help. It wasnt
there last time I read it probably in D2.
On 2 Sep 99 at 11:40, Aaron Scott-Boddendijk wrote:
> >> It's not the problem of NOT including the Borland shared Memory
> >> Manager if strings are being used?
> >> in the DLL uses st
Quoting Kerry Sainsbury <[EMAIL PROTECTED]>:
> *** REPLY SEPARATOR ***
>
> On 1/09/99 at 23:27 Nic Wise wrote:
>
> >> Tony Blomfield wrote:
> >>
> >> 1. For Interbase we have FIB and IBO
> >>
> >> 2. For Oracle we have ODA ?? Components.
> >
> >DOA, I beleive :) Direct Or
Quoting Nic Wise <[EMAIL PROTECTED]>:
> The are internal inprise ones. Quite nice, too, if you ask me, but there
> again, I dont have anything to compare them to :)
There seems to be a lot of ADO components around so it must be relatively
simple to implement.
snip
-
Thanks for the thoughts. The people who use my software are retailers, I expect they
will rarely if ever upgrade their PC. The software continues to work on the 'wrong
drive', except that new clients cant be added. Therefore the owner will have time to
contact the vendor without too much disruptio
If you go here http://www.netmastersllc.com/Upgrades/ and look at the bottom
under SMTP it says that the version that comes with Delphi does not support
anything other than plain text. If you want more you must buy the full
version from them for about US$200. :(
Incidentally, did you find anothe
>> It's not the problem of NOT including the Borland shared Memory
>> Manager if strings are being used?
>> in the DLL uses statements??
> No, thats only required for sharing long strings. Hmm. maybe it is.
> I will have another look at it later.
As the snippet from the help below states...
Leo,
you can always the idiotic Lotus method of the past. WHere the
instalaltion floppy was self modifying (repalce that with exe) and
could only be used once to install. If you wanted to move it to a
new pc, you uninstalled it which fixed the floppy and then re-
installed it.
The problem w
Kerry,
agree, which is why we dont use any of these schemes - they penalise
your paid-up user. That doesnt make sense to us.
Basically, you have to accept that some illegal copies will be made
and used. Depending on the type of software, there are other schemes.
In ours, we encourage them
No, thats only required for sharing long strings. Hmm. maybe it is.
I will have another look at it later.
On 31 Aug 99 at 16:02, Myles Penlington wrote:
> It's not the problem of NOT including the Borland shared Memory Manager if
> strings are being used?
> in the DLL uses statements??
>
>
The are internal inprise ones. Quite nice, too, if you ask me, but there
again, I dont have anything to compare them to :)
N
[EMAIL PROTECTED] wrote:
>
> Who does the ADOExpress components for Delphi 5 or are they Borland ones?
>
> ===
> Patrick Dunford
> --
Who does the ADOExpress components for Delphi 5 or are they Borland ones?
===
Patrick Dunford
---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.o
*** REPLY SEPARATOR ***
On 1/09/99 at 23:27 Nic Wise wrote:
>> Tony Blomfield wrote:
>>
>> 1. For Interbase we have FIB and IBO
>>
>> 2. For Oracle we have ODA ?? Components.
>
>DOA, I beleive :) Direct Oracle Access. Supposed to be quite good.
>
>> Does anybody know of si
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tony
BlomfieldSent: Wednesday, 1 September 1999 22:57To:
Multiple recipients of list delphiSubject: [DUG]: Thin Database
Components.
1. For Interbase we have FIB and IBO
2. For Oracle
> Tony Blomfield wrote:
>
> 1. For Interbase we have FIB and IBO
>
> 2. For Oracle we have ODA ?? Components.
DOA, I beleive :) Direct Oracle Access. Supposed to be quite good.
> Does anybody know of similar components for working with the Database
> API for SQL Server 7, and Informix?
1. For Interbase we have FIB and IBO
2. For Oracle we have ODA ?? Components.
Does anybody know of similar components for working with the
Database API for SQL Server 7, and Informix?
TIA,
Tony.
24 matches
Mail list logo
