Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Version 1 AEP's and ADS 8.1

5 posts in AEP Last posting was on 2007-06-14 22:47:51.0Z
Michael Meller Posted on 2007-06-12 08:56:57.0Z
Reply-To: "Michael Meller" <m.meller@futura-solutions.de>
From: "Michael Meller" <m.meller@futura-solutions.de>
Newsgroups: advantage.AEP
Subject: Version 1 AEP's and ADS 8.1
Date: Tue, 12 Jun 2007 10:56:57 +0200
Lines: 19
Organization: FUTURA Solutions
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 213.23.47.250
Message-ID: <466e5ec7@solutions.advantagedatabase.com>
X-Trace: 12 Jun 2007 02:52:23 -0700, 213.23.47.250
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.23.47.250
Xref: solutions.advantagedatabase.com Advantage.AEP:569
Article PK: 1103857

Hello,

I have written a bundle of V1 AEP's using the Delphi prototype from the
former tutotial. Everything was fine until ADS 8.0. Now under ADS 8.1
nothing works anymore (error 5154 at: tblInput.open).

What can I do to fix this? The Problem is we can't switch to V2. Several
customers still have ADS 6.2 running. So I am forced to work with the 6.2
Delphi components.

I read about a solution using AdsConnect60() and AdsOpenTable() for the
temporary input and output tables. Does this really work and is there an
example available? My first tries failed. Whitch database and whitch
tablenames do I have to use? I couldn't find any temporary input or output
table while debugging.

Michael


Jeremy Mullin Posted on 2007-06-13 14:25:16.0Z
Date: Wed, 13 Jun 2007 14:25:16 +0000 (UTC)
Message-ID: <e96e9af22d6f38c97bab816c0f00@devzone.advantagedatabase.com>
From: Jeremy Mullin <no@email.com>
Subject: Re: Version 1 AEP's and ADS 8.1
Newsgroups: Advantage.AEP
References: <466e5ec7@solutions.advantagedatabase.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-Newsreader: JetBrains Omea Reader 1098.1
NNTP-Posting-Host: 10.24.38.100
X-Trace: 13 Jun 2007 08:20:40 -0700, 10.24.38.100
Lines: 51
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.100
Xref: solutions.advantagedatabase.com Advantage.AEP:570
Article PK: 1103856

Hi Michael,

Yes, v1 AEPs were made obsolete in v8.1. As I think you already found, this
is from the readme:

* Version 1 AEPs are effectively obsolete with this release. If you
must use a version 1 AEP, there are now some limitations. 1) You
must use AdsOpenTable to open the input and output parameter
tables and pass ADS_TEMP_CURSOR_TABLE as the ulOptions flag. 2)
If the AEP is called from Advantage Database Server, you cannot
open the input and output parameter tables with Advantage Local
Server.

> there an example available? My first tries failed. Whitch database and
> whitch tablenames do I have to use?

I haven't tried it myself, but I believe the workaround involves using the
input and output table paths that are passed in to the AEP in a call to AdsOpenTable.
If you haven't got it working yet I can write and post an example.

The biggest pain will be reading the data from the table using ACE calls,
instead of TAdsTable methods. Ideally you could just call AdsOpenTable, and
then stuff that table handle into the input TAdsTable instance, but if you're
using older TDataSet components they won't have the SetHandle method that
is required to make that work.

J.D. Mullin
Advantage R&D



> Hello,
>
> I have written a bundle of V1 AEP's using the Delphi prototype from
> the former tutotial. Everything was fine until ADS 8.0. Now under ADS
> 8.1 nothing works anymore (error 5154 at: tblInput.open).
>
> What can I do to fix this? The Problem is we can't switch to V2.
> Several customers still have ADS 6.2 running. So I am forced to work
> with the 6.2 Delphi components.
>
> I read about a solution using AdsConnect60() and AdsOpenTable() for
> the temporary input and output tables. Does this really work and is
> there an example available? My first tries failed. Whitch database and
> whitch tablenames do I have to use? I couldn't find any temporary
> input or output table while debugging.
>
> Michael
>


Michael Meller Posted on 2007-06-14 10:53:11.0Z
Reply-To: "Michael Meller" <m.meller@futura-solutions.de>
From: "Michael Meller" <m.meller@futura-solutions.de>
Newsgroups: Advantage.AEP
References: <466e5ec7@solutions.advantagedatabase.com> <e96e9af22d6f38c97bab816c0f00@devzone.advantagedatabase.com>
Subject: Re: Version 1 AEP's and ADS 8.1
Date: Thu, 14 Jun 2007 12:53:11 +0200
Lines: 72
Organization: FUTURA Solutions
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
NNTP-Posting-Host: 213.23.47.250
Message-ID: <46711cfd@solutions.advantagedatabase.com>
X-Trace: 14 Jun 2007 04:48:29 -0700, 213.23.47.250
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.23.47.250
Xref: solutions.advantagedatabase.com Advantage.AEP:572
Article PK: 1103860

Hi Jeremy,

thanks for your infos.

As I had no success yet, an example that works with ADS 6.2 Delphi
components and ADS 6.2 to 8.1 Servers would be very, very nice.

ADS_TEMP_CURSOR_TABLE is unknown with 6.2 components, so I think we need the
value of this constant.

When I have the handles of the input and output tables I can manage the rest
with ADS API functions. Think this won't be a problem.

Best regards
Michael

"Jeremy Mullin" <no@email.com> schrieb im Newsbeitrag
news:e96e9af22d6f38c97bab816c0f00@devzone.advantagedatabase.com...

> Hi Michael,
>
> Yes, v1 AEPs were made obsolete in v8.1. As I think you already found,
> this is from the readme:
>
> * Version 1 AEPs are effectively obsolete with this release. If you
> must use a version 1 AEP, there are now some limitations. 1) You
> must use AdsOpenTable to open the input and output parameter
> tables and pass ADS_TEMP_CURSOR_TABLE as the ulOptions flag. 2)
> If the AEP is called from Advantage Database Server, you cannot
> open the input and output parameter tables with Advantage Local
> Server.
>
>> there an example available? My first tries failed. Whitch database and
>> whitch tablenames do I have to use?
>
> I haven't tried it myself, but I believe the workaround involves using the
> input and output table paths that are passed in to the AEP in a call to
> AdsOpenTable. If you haven't got it working yet I can write and post an
> example.
>
> The biggest pain will be reading the data from the table using ACE calls,
> instead of TAdsTable methods. Ideally you could just call AdsOpenTable,
> and then stuff that table handle into the input TAdsTable instance, but if
> you're using older TDataSet components they won't have the SetHandle
> method that is required to make that work.
>
> J.D. Mullin
> Advantage R&D
>
>
>
>> Hello,
>>
>> I have written a bundle of V1 AEP's using the Delphi prototype from
>> the former tutotial. Everything was fine until ADS 8.0. Now under ADS
>> 8.1 nothing works anymore (error 5154 at: tblInput.open).
>>
>> What can I do to fix this? The Problem is we can't switch to V2.
>> Several customers still have ADS 6.2 running. So I am forced to work
>> with the 6.2 Delphi components.
>>
>> I read about a solution using AdsConnect60() and AdsOpenTable() for
>> the temporary input and output tables. Does this really work and is
>> there an example available? My first tries failed. Whitch database and
>> whitch tablenames do I have to use? I couldn't find any temporary
>> input or output table while debugging.
>>
>> Michael
>>
>
>


Michael Meller Posted on 2007-06-14 13:11:11.0Z
Reply-To: "Michael Meller" <m.meller@futura-solutions.de>
From: "Michael Meller" <m.meller@futura-solutions.de>
Newsgroups: Advantage.AEP
References: <466e5ec7@solutions.advantagedatabase.com> <e96e9af22d6f38c97bab816c0f00@devzone.advantagedatabase.com>
Subject: Re: Version 1 AEP's and ADS 8.1
Date: Thu, 14 Jun 2007 15:11:11 +0200
Lines: 65
Organization: FUTURA Solutions
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
NNTP-Posting-Host: 213.23.47.250
Message-ID: <46713d62@solutions.advantagedatabase.com>
X-Trace: 14 Jun 2007 07:06:42 -0700, 213.23.47.250
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.23.47.250
Xref: solutions.advantagedatabase.com Advantage.AEP:573
Article PK: 1103861

Hi Jeremy,

thank's a lot. I made it with your example from the other thread. After I
learned, that AdsOpenTable needs the full path and not only the tablename it
worked!

Best regards
Michael

"Jeremy Mullin" <no@email.com> schrieb im Newsbeitrag
news:e96e9af22d6f38c97bab816c0f00@devzone.advantagedatabase.com...

> Hi Michael,
>
> Yes, v1 AEPs were made obsolete in v8.1. As I think you already found,
> this is from the readme:
>
> * Version 1 AEPs are effectively obsolete with this release. If you
> must use a version 1 AEP, there are now some limitations. 1) You
> must use AdsOpenTable to open the input and output parameter
> tables and pass ADS_TEMP_CURSOR_TABLE as the ulOptions flag. 2)
> If the AEP is called from Advantage Database Server, you cannot
> open the input and output parameter tables with Advantage Local
> Server.
>
>> there an example available? My first tries failed. Whitch database and
>> whitch tablenames do I have to use?
>
> I haven't tried it myself, but I believe the workaround involves using the
> input and output table paths that are passed in to the AEP in a call to
> AdsOpenTable. If you haven't got it working yet I can write and post an
> example.
>
> The biggest pain will be reading the data from the table using ACE calls,
> instead of TAdsTable methods. Ideally you could just call AdsOpenTable,
> and then stuff that table handle into the input TAdsTable instance, but if
> you're using older TDataSet components they won't have the SetHandle
> method that is required to make that work.
>
> J.D. Mullin
> Advantage R&D
>
>
>
>> Hello,
>>
>> I have written a bundle of V1 AEP's using the Delphi prototype from
>> the former tutotial. Everything was fine until ADS 8.0. Now under ADS
>> 8.1 nothing works anymore (error 5154 at: tblInput.open).
>>
>> What can I do to fix this? The Problem is we can't switch to V2.
>> Several customers still have ADS 6.2 running. So I am forced to work
>> with the 6.2 Delphi components.
>>
>> I read about a solution using AdsConnect60() and AdsOpenTable() for
>> the temporary input and output tables. Does this really work and is
>> there an example available? My first tries failed. Whitch database and
>> whitch tablenames do I have to use? I couldn't find any temporary
>> input or output table while debugging.
>>
>> Michael
>>
>
>