Tim,

Best wishes to your father!

Have you checked the 'issue' of refreshing views yet (and if it's an issue -
will it be fixed in 1.06)?

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:B341D1FC-CFC2-41FC-9754-6D4EFE009DC0@news.elevatesoft.com...
> Chris,
>
> << You appear to be having a very long day of building and testing over
> there <vbg>. >>
>
> The documentation is taking a bit longer than expected, and my father had
to
> have surgery this week for an obstructed bowel (that whole affair started
on
> Monday).  Between the two, it's been a dismal week for getting it done.
>
> << When 1.06 is out is there any planned order of completion (or time
scale)
> for the following:
>
>  1) ADO driver
> 2) RANGE (or LIMIT) in the SQL >>
>
> Both will be done at the same time, although the range/limit functionality
> will not be SQL-based.  More than likely it will be handled in the
> EDBDataReader class.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Tim,

Your father is definitely more important. Hope he is doing better.

--
Regards,
Jan Ferguson


Tim Young [Elevate Software] wrote:

<<The documentation is taking a bit longer than expected, and my father
<<had to have surgery this week for an obstructed bowel (that whole
<<affair started on Monday).  Between the two, it's been a dismal week
<<for getting it done.

Roy,

<< Sympathy and best wishes to your father >>

Thanks.  It wasn't anything major, but since his heart attack any surgery
isn't particularly welcome.

--
Tim Young
Elevate Software
www.elevatesoft.com

Chris,

<< Sorry to hear about your father, hope he recovers soon. >>

Thanks.  He's a fighter, so I don't have any doubts that he'll be back on
his feet soon.

<< If the Range/Limit is not done via SQL, am I still going to have access
to this function via the ODBC/ADO drivers? >>

That's a little bit of an issue since the generic ODBC calls don't really
provide for this type of extension.  More than likely it will have to be
done with a {} extension in the SQL that is stripped out and processed
separately.  The main idea is to eliminate paging from the SQL syntax, since
having it there requires all sorts of parsing and comparisons to simply
determine if the only thing that changed is the range specification, and
many front-end components and APIs like ODBC don't make allowances for such
a change without requiring a complete re-preparation of the query.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jan,

<< Your father is definitely more important. Hope he is doing better. >>

Thanks.  He should be out of ICU today or tomorrow.  They put him there
because they wanted him on a ventilator due to the pain involved with
breathing due to the abdominal surgery.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fons,

<< Good health and wishes to your father. >>

Thanks.

<< BTW, I needed to google for obstructed bowel. Hope he is feeling better
soon. >>

In his case it was an old hernia surgery where they used a type of "netting"
to hold an abdominal hernia in place.  This netting broke a few years back
and since then a piece of it wrapped around his bowel, causing the complete
blockage.  Another case of the cure being worse than the original problem.

--
Tim Young
Elevate Software
www.elevatesoft.com

Harry,

<< Best wishes to your father! >>

Thanks.

<< Have you checked the 'issue' of refreshing views yet (and if it's an
issue - will it be fixed in 1.06)? >>

Yep.  It's a bug - the view/query refreshing works within the same session,
but not across sessions.  It will be fixed in 1.06.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Sorry about your father, best wishes from here also

Regards,
Hüseyin

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i en
meddelelse news:440967E9-3011-496B-AA64-64D20A9D1714@news.elevatesoft.com...
> Jan,
>
> << Your father is definitely more important. Hope he is doing better. >>
>
> Thanks.  He should be out of ICU today or tomorrow.  They put him there
> because they wanted him on a ventilator due to the pain involved with
> breathing due to the abdominal surgery.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tim,

> Yep.  It's a bug - the view/query refreshing works within the same
session,
> but not across sessions.  It will be fixed in 1.06.

Great!

Regards, Harry


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:17919EB3-2CD3-4903-B2B7-F3FA3582556A@news.elevatesoft.com...
> Harry,
>
> << Best wishes to your father! >>
>
> Thanks.
>
> << Have you checked the 'issue' of refreshing views yet (and if it's an
> issue - will it be fixed in 1.06)? >>
>
> Yep.  It's a bug - the view/query refreshing works within the same
session,
> but not across sessions.  It will be fixed in 1.06.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Although the Range/Limit feature would be nice, I could live with just
the old TOP facility, that is what I am using at the moment with the
DBISAM 4 ODBC driver.

Chris

> That's a little bit of an issue since the generic ODBC calls don't really
> provide for this type of extension.  More than likely it will have to be
> done with a {} extension in the SQL that is stripped out and processed
> separately.  The main idea is to eliminate paging from the SQL syntax, since
> having it there requires all sorts of parsing and comparisons to simply
> determine if the only thing that changed is the range specification, and
> many front-end components and APIs like ODBC don't make allowances for such
> a change without requiring a complete re-preparation of the query.
>