Interface between Ada (AdaCore 6.1) and Microsoft Access Database (PC/XP)

Interface between Ada (AdaCore 6.1) and Microsoft Access Database (PC/XP)

[shulamith.sarfaty]

Please show me an example how to manipulate record sets from
Microsoft Access Database. We need to open a connection,
execute an SQL statement to UPDATE, INSERT, DELETE and/or SELECT
records from the database. Also, I dynamically create a
variable string containing my SQL statement. I want to
execute an SQL string which is variable in length. How do I free
the pointer to that string?
Thanks.

Re: Interface between Ada (AdaCore 6.1) and Microsoft Access Database (PC/XP)

[Jeffrey R. Carter]

shulamith.sarfaty@baesystems.com wrote:
> Please show me an example how to manipulate record sets from
> Microsoft Access Database. We need to open a connection,
> execute an SQL statement to UPDATE, INSERT, DELETE and/or SELECT
> records from the database. Also, I dynamically create a
> variable string containing my SQL statement. I want to
> execute an SQL string which is variable in length. How do I free
> the pointer to that string?

What DB binding are you using? And why would you use a pointer and risk memory 
leaks when you don't need to?

-- 
Jeff Carter
"Ah, go away or I'll kill ya."
Never Give a Sucker an Even Break
100

Re: Interface between Ada (AdaCore 6.1) and Microsoft Access Database (PC/XP)

[Dmitry A. Kazakov]

On Wed, 3 Dec 2008 07:33:41 -0800 (PST), shulamith.sarfaty@baesystems.com
wrote:

> Please show me an example how to manipulate record sets from
> Microsoft Access Database. We need to open a connection,
> execute an SQL statement to UPDATE, INSERT, DELETE and/or SELECT
> records from the database.

Take a look at GNADE ODBC, which is Ada binding to ODBC.

> Also, I dynamically create a
> variable string containing my SQL statement. I want to
> execute an SQL string which is variable in length. How do I free
> the pointer to that string?

Create it on the stack and you will need not to care about freeing it. It
is also recommended to use precompiled (so-called "prepared") statements
rather than reinterpret it each time.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de