Should I expect any problems with application that was built with Delphi 6,
DBISAM 3.30, when it will run on a Vista machine? Additionaly, the
application is local, with no file sharing.

Thank you,
Janusz Cyran

Hi Janusz,

Can't answer this for sure, but I've used D7 with Edisoft apps on Vista,
with no issues (releating to Edisoft that is). No guarantee, but for what
it's worth...

Cheers

Adam.

"Janusz Cyran" <lobster@hot.pl> wrote in message
news:F65483C7-A4E1-43CC-BF76-5E979C0FACE0@news.elevatesoft.com...
> Should I expect any problems with application that was built with Delphi
> 6, DBISAM 3.30, when it will run on a Vista machine? Additionaly, the
> application is local, with no file sharing.
>
> Thank you,
> Janusz Cyran
>
>

Janusz,

<< Should I expect any problems with application that was built with Delphi
6, DBISAM 3.30, when it will run on a Vista machine? Additionaly, the
application is local, with no file sharing. >>

We've seen some issues with sorting with some collations due to changes in
the collations in Vista.  Are you using the ANSI Standard collation, or
something specific ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I use NewLanguageID = 1045 and NewSortID =  0. BTW, I cannot find The
NewLanguageID parameter values list in the latest DBISAM 3.30 manual.

Janusz


> << Should I expect any problems with application that was built with
> Delphi 6, DBISAM 3.30, when it will run on a Vista machine? Additionaly,
> the application is local, with no file sharing. >>
>
> We've seen some issues with sorting with some collations due to changes in
> the collations in Vista.  Are you using the ANSI Standard collation, or
> something specific ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Janusz,

<< I use NewLanguageID = 1045 and NewSortID =  0. BTW, I cannot find The
NewLanguageID parameter values list in the latest DBISAM 3.30 manual. >>

As far as I know, the Polish language is okay with both.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Janusz,
This post is coming in a little late.

I have a few apps developed in Delphi6/ DBISam V3.3. These apps have been
successfully deployed on Vista machines. The thing you need to be carefull
about is if your app calls RestructureTable or AlterTable. After this is
done, if the Vista user logs in with another Windows user account, he/ she
may not have Windows permissions to open the the table. The user can only
open the table with the same window user account used when RestructureTable
AlterTable was run. If you search this NG you may be able to find more posts
on this.

Regards
Gregory Sebastian

Hi Gregory,

Thank you. Seems annoying, I will try to find the relevant posts.

Best regards,
Janusz



Gregory Sebastian napisał(a):
> Hi Janusz,
> This post is coming in a little late.
>
> I have a few apps developed in Delphi6/ DBISam V3.3. These apps have
> been successfully deployed on Vista machines. The thing you need to be
> carefull about is if your app calls RestructureTable or AlterTable.
> After this is done, if the Vista user logs in with another Windows user
> account, he/ she may not have Windows permissions to open the the table.
> The user can only open the table with the same window user account used
> when RestructureTable AlterTable was run. If you search this NG you may
> be able to find more posts on this.
>
> Regards
> Gregory Sebastian

Gregory,

<< I have a few apps developed in Delphi6/ DBISam V3.3. These apps have been
successfully deployed on Vista machines. The thing you need to be carefull
about is if your app calls RestructureTable or AlterTable. After this is
done, if the Vista user logs in with another Windows user account, he/ she
may not have Windows permissions to open the the table. The user can only
open the table with the same window user account used when RestructureTable
AlterTable was run. If you search this NG you may be able to find more posts
on this. >>

This was also the case with XP:

http://www.elevatesoft.com/bulletin_9.htm

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Janusz,
A quick way to get around it is to set your PrivateDir property to the
database folder just before RestructureTable or AlterTable is called then
set it back to the local temp folder again after. If your database will
always be local, you may as well leave your PrivateDir permanantly at the
database folder location.

Regards
Gregory Sebastian

Hi Tim,

>> This was also the case with XP:

Yes but it seems to be much more apparent in Vista now. In XP, this problem
did not show up if the user logs in with any Adminstrator account. In Vista,
with UAC enabled (default setting) it shows up even when a user logs in to
Windows with any account including Administrator accounts.

Regards
Gregory Sebastian