I have the eval for Alaska. Looks good, so far. Some of the post on this
site concern me though and I'm not ready to jump on the wagon yet. Does
anyone out there have some quick, short  and nasty apps done in Xbase++ that
shows connectivity with ADS either on W2kserver or Linux. I have 7.0 running
on Windows and 8.0 on Linux. I would like to see examples on how this is
integrated and implemented. I do well with examples and not so well with
general stuff like "just use the API's"

ken

Ken,

The explanation on using ADS with Xbase++ in three easy steps-

1) Load ADSDBE in your dbesys.prg startup module and make it your default 
database engine (DBE).
2) Open a DacSession() at the beginning of your application (per 
instructions below) to your database server.
3) Program as you normally would using standard xBase syntax.

Note: Using multiple ADS servers requires changing the active DacSession() 
prior to each table use.

Rodd

Straight from the Xbase++ v1.90 RC2 docs.  The numbered lines are the 
samples:

Server identification
When using DacConnect() to establish a connection to the ADS Server there 
must be a way to identify the server. Therefore different ways are available 
to identify the server.
Using mapped/used drive
Using Server-Drive is the easiest way to indentify the ADS Server. However, 
the drawback of this approach is that the local workstation accessing the 
files has been forced to have the drive mapped to the file-server the ADS 
Server is installed on.

01: DacSession():New("DBE=ADSDBE;SERVER=F:")

Server and share names
Using Servername and Sharename as a way to specify the server location in 
the connection string, the workstation accessing the server does no longer 
need the drive being mapped. However the user has to be successfully 
authentificated by the server hosting the ADS Server.

01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\SOMEWHERE")

Dictionary connection using path and filename to dictionary storage
When using Advantage Database Server 6.x or higher one can connect to the 
server and open a dictionary connection using the full UNC pathname and 
filename where the dictionary resides. If connections to the dictionary are 
required in most cases additional user and password authentification may be 
required.

01: DacSession():New("DBE=ADSDBE";SERVER=\\ALASKA01\SOMEWHERE\Product 
Group.add")

Dictionary connection using alias-name
The ADS Server allows access to a dictionary without knowing the physical 
location of the dictionary and its related database files. To connect to the 
ADS Server, one must specify the alias-name of the dictionary straight after 
the servername. The following code illustrates this method of establishing a 
connection.

01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\ProductGroup")

Connections through the intranet (TCP/IP) or to Linux
Connection paths to the Advantage Database Server can also be composed out 
of an domain-name or ip-address and an optional port number. The port number 
must be specified if the ADS Server is configured to a specific port. The IP 
address must be used when the domain name of the server can not resolved 
using an available DNS service.

01: 
DacSession():New("DBE=ADSDBE;SERVER=\\ads70.alaska-software.com:6200\ProductGroup")

02: DacSession():New("DBE=ADSDBE;SERVER=\\192.168.2.1:6200\ProductGroup")

Connections through the internet
Connections through the internet (extranet) are a specific type of an TCP/IP 
connection. Additional attributes such as ADS_AIS_SERVER and the IP Port are 
necessary. The following connection string establishes a connection via the 
internet to the public demo server from extended systems. The ADS_AIS_SERVER 
connection attribute is required for internet connections, if not specified 
the server will refuse the connect.

01: DacSession():New("DBE=ADSDBE;"+;
02: 
"SERVER=\\devzone.advantagedatabase.com:4001\addressdata\DD\AIS_demo.ADD;"+;

03:                  "ADS_AIS_SERVER;UID=demo;PWD=demo;")

"Ken Brown" <krown.kpb@gmailcom> wrote in message 
news:27e2c15$74b19f27$ed45@news.alaska-software.com...
>I have the eval for Alaska. Looks good, so far. Some of the post on this
> site concern me though and I'm not ready to jump on the wagon yet. Does
> anyone out there have some quick, short  and nasty apps done in Xbase++ 
> that
> shows connectivity with ADS either on W2kserver or Linux. I have 7.0 
> running
> on Windows and 8.0 on Linux. I would like to see examples on how this is
> integrated and implemented. I do well with examples and not so well with
> general stuff like "just use the API's"
>
> ken
>
>

Rodd Graham wrote:
> Ken,
> 
> The explanation on using ADS with Xbase++ in three easy steps-
> 
> 1) Load ADSDBE in your dbesys.prg startup module and make it your default 
> database engine (DBE).
> 2) Open a DacSession() at the beginning of your application (per 
> instructions below) to your database server.
> 3) Program as you normally would using standard xBase syntax.
> 
> Note: Using multiple ADS servers requires changing the active DacSession() 
> prior to each table use.
> 
> Rodd
> 
> Straight from the Xbase++ v1.90 RC2 docs.  The numbered lines are the 
> samples:
> 
> Server identification
> When using DacConnect() to establish a connection to the ADS Server there 
> must be a way to identify the server. Therefore different ways are available 
> to identify the server.
> Using mapped/used drive
> Using Server-Drive is the easiest way to indentify the ADS Server. However, 
> the drawback of this approach is that the local workstation accessing the 
> files has been forced to have the drive mapped to the file-server the ADS 
> Server is installed on.
> 
> 01: DacSession():New("DBE=ADSDBE;SERVER=F:")
> 
> Server and share names
> Using Servername and Sharename as a way to specify the server location in 
> the connection string, the workstation accessing the server does no longer 
> need the drive being mapped. However the user has to be successfully 
> authentificated by the server hosting the ADS Server.
> 
> 01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\SOMEWHERE")
> 
> Dictionary connection using path and filename to dictionary storage
> When using Advantage Database Server 6.x or higher one can connect to the 
> server and open a dictionary connection using the full UNC pathname and 
> filename where the dictionary resides. If connections to the dictionary are 
> required in most cases additional user and password authentification may be 
> required.
> 
> 01: DacSession():New("DBE=ADSDBE";SERVER=\\ALASKA01\SOMEWHERE\Product 
> Group.add")
> 
> Dictionary connection using alias-name
> The ADS Server allows access to a dictionary without knowing the physical 
> location of the dictionary and its related database files. To connect to the 
> ADS Server, one must specify the alias-name of the dictionary straight after 
> the servername. The following code illustrates this method of establishing a 
> connection.
> 
> 01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\ProductGroup")
> 
> Connections through the intranet (TCP/IP) or to Linux
> Connection paths to the Advantage Database Server can also be composed out 
> of an domain-name or ip-address and an optional port number. The port number 
> must be specified if the ADS Server is configured to a specific port. The IP 
> address must be used when the domain name of the server can not resolved 
> using an available DNS service.
> 
> 01: 
> DacSession():New("DBE=ADSDBE;SERVER=\\ads70.alaska-software.com:6200\ProductGroup")
> 
> 02: DacSession():New("DBE=ADSDBE;SERVER=\\192.168.2.1:6200\ProductGroup")
> 
> Connections through the internet
> Connections through the internet (extranet) are a specific type of an TCP/IP 
> connection. Additional attributes such as ADS_AIS_SERVER and the IP Port are 
> necessary. The following connection string establishes a connection via the 
> internet to the public demo server from extended systems. The ADS_AIS_SERVER 
> connection attribute is required for internet connections, if not specified 
> the server will refuse the connect.
> 
> 01: DacSession():New("DBE=ADSDBE;"+;
> 02: 
> "SERVER=\\devzone.advantagedatabase.com:4001\addressdata\DD\AIS_demo.ADD;"+;
> 
> 03:                  "ADS_AIS_SERVER;UID=demo;PWD=demo;")
> 
> "Ken Brown" <krown.kpb@gmailcom> wrote in message 
> news:27e2c15$74b19f27$ed45@news.alaska-software.com...
> 
>>I have the eval for Alaska. Looks good, so far. Some of the post on this
>>site concern me though and I'm not ready to jump on the wagon yet. Does
>>anyone out there have some quick, short  and nasty apps done in Xbase++ 
>>that
>>shows connectivity with ADS either on W2kserver or Linux. I have 7.0 
>>running
>>on Windows and 8.0 on Linux. I would like to see examples on how this is
>>integrated and implemented. I do well with examples and not so well with
>>general stuff like "just use the API's"
>>
>>ken
>>
>>
> 
> 
> 
And it works good.  I am using on netware with ADS 6.11 but it works 
great and also coexists with the original clipper application while it 
is being converted.

Sounds good, but adsdbe was not included in demo. I went to the adsdbe page
a downloaded the demo from the link indicated but it did not include any ads
libs.

Ken


"Rodd Graham" <rodd@grahamautomation.com> wrote in message
news:472c6e33$5e62f1b3$1415b@news.alaska-software.com...
> Ken,
>
> The explanation on using ADS with Xbase++ in three easy steps-
>
> 1) Load ADSDBE in your dbesys.prg startup module and make it your default
> database engine (DBE).
> 2) Open a DacSession() at the beginning of your application (per
> instructions below) to your database server.
> 3) Program as you normally would using standard xBase syntax.
>
> Note: Using multiple ADS servers requires changing the active DacSession()
> prior to each table use.
>
> Rodd
>
> Straight from the Xbase++ v1.90 RC2 docs.  The numbered lines are the
> samples:
>
> Server identification
> When using DacConnect() to establish a connection to the ADS Server there
> must be a way to identify the server. Therefore different ways are
available
> to identify the server.
> Using mapped/used drive
> Using Server-Drive is the easiest way to indentify the ADS Server.
However,
> the drawback of this approach is that the local workstation accessing the
> files has been forced to have the drive mapped to the file-server the ADS
> Server is installed on.
>
> 01: DacSession():New("DBE=ADSDBE;SERVER=F:")
>
> Server and share names
> Using Servername and Sharename as a way to specify the server location in
> the connection string, the workstation accessing the server does no longer
> need the drive being mapped. However the user has to be successfully
> authentificated by the server hosting the ADS Server.
>
> 01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\SOMEWHERE")
>
> Dictionary connection using path and filename to dictionary storage
> When using Advantage Database Server 6.x or higher one can connect to the
> server and open a dictionary connection using the full UNC pathname and
> filename where the dictionary resides. If connections to the dictionary
are
> required in most cases additional user and password authentification may
be
> required.
>
> 01: DacSession():New("DBE=ADSDBE";SERVER=\\ALASKA01\SOMEWHERE\Product
> Group.add")
>
> Dictionary connection using alias-name
> The ADS Server allows access to a dictionary without knowing the physical
> location of the dictionary and its related database files. To connect to
the
> ADS Server, one must specify the alias-name of the dictionary straight
after
> the servername. The following code illustrates this method of establishing
a
> connection.
>
> 01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\ProductGroup")
>
> Connections through the intranet (TCP/IP) or to Linux
> Connection paths to the Advantage Database Server can also be composed out
> of an domain-name or ip-address and an optional port number. The port
number
> must be specified if the ADS Server is configured to a specific port. The
IP
> address must be used when the domain name of the server can not resolved
> using an available DNS service.
>
> 01:
>
DacSession():New("DBE=ADSDBE;SERVER=\\ads70.alaska-software.com:6200\Product
Group")
>
> 02: DacSession():New("DBE=ADSDBE;SERVER=\\192.168.2.1:6200\ProductGroup")
>
> Connections through the internet
> Connections through the internet (extranet) are a specific type of an
TCP/IP
> connection. Additional attributes such as ADS_AIS_SERVER and the IP Port
are
> necessary. The following connection string establishes a connection via
the
> internet to the public demo server from extended systems. The
ADS_AIS_SERVER
> connection attribute is required for internet connections, if not
specified
> the server will refuse the connect.
>
> 01: DacSession():New("DBE=ADSDBE;"+;
> 02:
>
"SERVER=\\devzone.advantagedatabase.com:4001\addressdata\DD\AIS_demo.ADD;"+;
>
> 03:                  "ADS_AIS_SERVER;UID=demo;PWD=demo;")
>
> "Ken Brown" <krown.kpb@gmailcom> wrote in message
> news:27e2c15$74b19f27$ed45@news.alaska-software.com...
> >I have the eval for Alaska. Looks good, so far. Some of the post on this
> > site concern me though and I'm not ready to jump on the wagon yet. Does
> > anyone out there have some quick, short  and nasty apps done in Xbase++
> > that
> > shows connectivity with ADS either on W2kserver or Linux. I have 7.0
> > running
> > on Windows and 8.0 on Linux. I would like to see examples on how this is
> > integrated and implemented. I do well with examples and not so well with
> > general stuff like "just use the API's"
> >
> > ken
> >
> >
>
>

ADSDBE is included with the Professional edition but I believe you can 
purchase it separately. I doubt there is a demo version available If 
there is you would need to get it directly from Alaska ie email them.

Jim

Ken Brown wrote:
> Sounds good, but adsdbe was not included in demo. I went to the adsdbe page
> a downloaded the demo from the link indicated but it did not include any ads
> libs.
> 
> Ken
> 
> 
> "Rodd Graham" <rodd@grahamautomation.com> wrote in message
> news:472c6e33$5e62f1b3$1415b@news.alaska-software.com...
> 
>>Ken,
>>
>>The explanation on using ADS with Xbase++ in three easy steps-
>>
>>1) Load ADSDBE in your dbesys.prg startup module and make it your default
>>database engine (DBE).
>>2) Open a DacSession() at the beginning of your application (per
>>instructions below) to your database server.
>>3) Program as you normally would using standard xBase syntax.
>>
>>Note: Using multiple ADS servers requires changing the active DacSession()
>>prior to each table use.
>>
>>Rodd
>>
>>Straight from the Xbase++ v1.90 RC2 docs.  The numbered lines are the
>>samples:
>>
>>Server identification
>>When using DacConnect() to establish a connection to the ADS Server there
>>must be a way to identify the server. Therefore different ways are
> 
> available
> 
>>to identify the server.
>>Using mapped/used drive
>>Using Server-Drive is the easiest way to indentify the ADS Server.
> 
> However,
> 
>>the drawback of this approach is that the local workstation accessing the
>>files has been forced to have the drive mapped to the file-server the ADS
>>Server is installed on.
>>
>>01: DacSession():New("DBE=ADSDBE;SERVER=F:")
>>
>>Server and share names
>>Using Servername and Sharename as a way to specify the server location in
>>the connection string, the workstation accessing the server does no longer
>>need the drive being mapped. However the user has to be successfully
>>authentificated by the server hosting the ADS Server.
>>
>>01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\SOMEWHERE")
>>
>>Dictionary connection using path and filename to dictionary storage
>>When using Advantage Database Server 6.x or higher one can connect to the
>>server and open a dictionary connection using the full UNC pathname and
>>filename where the dictionary resides. If connections to the dictionary
> 
> are
> 
>>required in most cases additional user and password authentification may
> 
> be
> 
>>required.
>>
>>01: DacSession():New("DBE=ADSDBE";SERVER=\\ALASKA01\SOMEWHERE\Product
>>Group.add")
>>
>>Dictionary connection using alias-name
>>The ADS Server allows access to a dictionary without knowing the physical
>>location of the dictionary and its related database files. To connect to
> 
> the
> 
>>ADS Server, one must specify the alias-name of the dictionary straight
> 
> after
> 
>>the servername. The following code illustrates this method of establishing
> 
> a
> 
>>connection.
>>
>>01: DacSession():New("DBE=ADSDBE;SERVER=\\ALASKA01\ProductGroup")
>>
>>Connections through the intranet (TCP/IP) or to Linux
>>Connection paths to the Advantage Database Server can also be composed out
>>of an domain-name or ip-address and an optional port number. The port
> 
> number
> 
>>must be specified if the ADS Server is configured to a specific port. The
> 
> IP
> 
>>address must be used when the domain name of the server can not resolved
>>using an available DNS service.
>>
>>01:
>>
> 
> DacSession():New("DBE=ADSDBE;SERVER=\\ads70.alaska-software.com:6200\Product
> Group")
> 
>>02: DacSession():New("DBE=ADSDBE;SERVER=\\192.168.2.1:6200\ProductGroup")
>>
>>Connections through the internet
>>Connections through the internet (extranet) are a specific type of an
> 
> TCP/IP
> 
>>connection. Additional attributes such as ADS_AIS_SERVER and the IP Port
> 
> are
> 
>>necessary. The following connection string establishes a connection via
> 
> the
> 
>>internet to the public demo server from extended systems. The
> 
> ADS_AIS_SERVER
> 
>>connection attribute is required for internet connections, if not
> 
> specified
> 
>>the server will refuse the connect.
>>
>>01: DacSession():New("DBE=ADSDBE;"+;
>>02:
>>
> 
> "SERVER=\\devzone.advantagedatabase.com:4001\addressdata\DD\AIS_demo.ADD;"+;
> 
>>03:                  "ADS_AIS_SERVER;UID=demo;PWD=demo;")
>>
>>"Ken Brown" <krown.kpb@gmailcom> wrote in message
>>news:27e2c15$74b19f27$ed45@news.alaska-software.com...
>>
>>>I have the eval for Alaska. Looks good, so far. Some of the post on this
>>>site concern me though and I'm not ready to jump on the wagon yet. Does
>>>anyone out there have some quick, short  and nasty apps done in Xbase++
>>>that
>>>shows connectivity with ADS either on W2kserver or Linux. I have 7.0
>>>running
>>>on Windows and 8.0 on Linux. I would like to see examples on how this is
>>>integrated and implemented. I do well with examples and not so well with
>>>general stuff like "just use the API's"
>>>
>>>ken
>>>
>>>
>>
>>
> 
>

Purchase the Professional Edition, which includes ADSDBE, and don't look 
back. You'll be please with the results.

Or. Convert to Delphi.

Or. Re-write from the ground up in .NET.

We have 1200 users using a Clipper/ADS app. that was implemented a year ago. 
We had our first corrupted index a week ago. (The program is used form 6 
a.m. to 11 p.m. six days a week.) We have 300 users using a 
converted-from-Clipper Alaska/ADS app. that was implemented 3 months ago. It 
works the same, only faster.

Hint: If you create large temporary files on a local drive, use the ADS 
Local Server to manipulate those files; it's much faster than the DBFCDX DBE 
in Alaska.

HTH
Tim

"Ken Brown" <krown.kpb@gmailcom> wrote in message 
news:27e2c15$74b19f27$ed45@news.alaska-software.com...
>I have the eval for Alaska. Looks good, so far. Some of the post on this
> site concern me though and I'm not ready to jump on the wagon yet. Does
> anyone out there have some quick, short  and nasty apps done in Xbase++ 
> that
> shows connectivity with ADS either on W2kserver or Linux. I have 7.0 
> running
> on Windows and 8.0 on Linux. I would like to see examples on how this is
> integrated and implemented. I do well with examples and not so well with
> general stuff like "just use the API's"
>
> ken
>
>

I'm having the same problem....its hard to evaluate when you can't really
test it.



*********************************************
Don Schmitz
University Hospital Surgery Dept.
600 Highland Ave. F8-164
Madison, WI  53792
(608) 263-9307
Email: Dons@surgery.wisc.edu