Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 11 of 11 total
Thread 3.30 and Vista: solved!
Mon, Jan 14 2008 8:59 AMPermanent Link

carlosam
I'm sure there are lot of dbisam clients with the same problem and we all work for money.
It is fair that we pay Elevate for a ver 3 upgrade.
If we are not compatible with Vista we are not compatible with Windows and as out
perspectives clients see us as obsolete solution.

I would pay for the upgrade because  Vista is not Elevated fault. I
To upgrade to Elevate new database mean lots of hours of work and beta problems. I rather
pay for a ver3 for Vista.
If I buy ElevatedDB and have the dbisam for Vista it would be a great deal.

Carlos



Jan Hornstrup <jhc@soft-team.dk> wrote:

Hi Avalon.

It is correct, that checking the XPSP2 will solve all strange behaivor of DBISAM-3 tables
and SQL.

BUT - BUT - BUT     

unfortunately this features is not enabled, when the executeable program is stored on a
shared network drive. It only work, when the program is on a local harddrive !!!

If you have any solution to this, PLEASE let me know as I also have 100's of installations
to update.

Brgds

Jan Hornstrup
Denmark
Email: jhc@soft-team.dk





"Avalon" <funny@funny.com> wrote:

For you users of the "old" version. I've just found an annoying problem
using 3.30 under Vista, which required 6 hrs of investigation to solve.
Master/detail tables, when detail uses a double-or-multiple-field index (for
example an integer key to refer to master field + a date field to obtain a
date-sorted detail record list) simply don't work: details results always
empty. The same table/procedure under XP works fine. The solution: check the
"XPSP2" checkbox under the executable properties, and all works again.
Anyone has an explanation for such problem? Note that using a single-field
index for detail works fine even under Vista.

Avalon

« Previous PagePage 2 of 2
Jump to Page:  1 2
Image