Hi

Delphi XE6/Win7/DBIsam C/S 4.43 b1

Getting this error at startup of application.

1. I made some changes to an application.
2. Uploaded this to the client site (win7 64 bit) and ran the app that now gives above error.
(The old (before update) app works fine on the client site - so for now I have reverted back to old one)

Funny thing is that the same app works and loads ok on my pc.

Wonder what has changed here to cause this to happen.?

Is there some logic to this ? Just does not make any sense !

Regards


Kamran

kamran wrote:

> Wonder what has changed here to cause this to happen.?

Most likely you left the database/table open in the IDE, and so on
creating the form it tries to connect and it is in a different location
on the other PC. Your code probably sets the location properly, but it
doesn't get a chance to run before the components are created.

I have actions in my build scripts to ensure database.Active is false,
etc.

--

Matthew Jones

Hi Matthew

1. So the location folders for app are the same on my pc as well as the client pc

2. Client is a windows 8 PC .. not a win 7 pc as quoted before.

3. I checked that the file is closed .ie active is false (by default)

thanks

Kamran

"Matthew Jones" wrote:

kamran wrote:

> Wonder what has changed here to cause this to happen.?

Most likely you left the database/table open in the IDE, and so on
creating the form it tries to connect and it is in a different location
on the other PC. Your code probably sets the location properly, but it
doesn't get a chance to run before the components are created.

I have actions in my build scripts to ensure database.Active is false,
etc.

--

Matthew Jones

kamran wrote:

> 1. So the location folders for app are the same on my pc as well as
> the client pc
>
> 2. Client is a windows 8 PC .. not a win 7 pc as quoted before.
>
> 3. I checked that the file is closed .ie active is false (by default)

I suggest using something like madExcept then to see exactly where it
is failing, and how. Adding in some logging if you have such available
would allow you to see the paths etc. Basically, there is no magic
solution other than investigation.

--

Matthew Jones

"Matthew Jones" wrote:

kamran wrote:

> 1. So the location folders for app are the same on my pc as well as
> the client pc
>
> 2. Client is a windows 8 PC .. not a win 7 pc as quoted before.
>
> 3. I checked that the file is closed .ie active is false (by default)

I suggest using something like madExcept then to see exactly where it
is failing, and how. Adding in some logging if you have such available
would allow you to see the paths etc. Basically, there is no magic
solution other than investigation.

--

Matthew Jones

Hi Matthew

Just in case anybody else has this issue.

I just checked the versions of DBIsam on client and and my pc
and there was a mismatch. of 4.42 b2 and 4.43 b1

I have corrected this. And this seems to have done the trick.

Thanks again

kamran wrote:

"Matthew Jones" wrote:

kamran wrote:

> 1. So the location folders for app are the same on my pc as well as
> the client pc
>
> 2. Client is a windows 8 PC .. not a win 7 pc as quoted before.
>
> 3. I checked that the file is closed .ie active is false (by default)

I suggest using something like madExcept then to see exactly where it
is failing, and how. Adding in some logging if you have such available
would allow you to see the paths etc. Basically, there is no magic
solution other than investigation.

--

Matthew Jones

kamran


I'd pretty much agree with Matthew here. If the tables on the two different PCs have the exact same path then

1) check permissions
2) make sure the database / path is set correctly for the table before its opened.
3) make sure its a directory that can be used for data - Windows has been altering things and it may be where you're storing your data is no longer allowed

Roy Lambert

Thanks Roy

As I replied to Matthew..

It appears to be in my case to be dibisam versioning issue.
Which I corrected and now all seems to be ok.
Slightly puzzling but true !

Cheers

Kamran

Roy Lambert wrote:

kamran


I'd pretty much agree with Matthew here. If the tables on the two different PCs have the exact same path then

1) check permissions
2) make sure the database / path is set correctly for the table before its opened.
3) make sure its a directory that can be used for data - Windows has been altering things and it may be where you're storing your data is no longer allowed

Roy Lambert

On 6/15/2016 7:52 AM, kamran wrote:
> Just in case anybody else has this issue.
> I just checked the versions of DBIsam on client and and my pc
> and there was a mismatch. of 4.42 b2 and 4.43 b1
> I have corrected this. And this seems to have done the trick.

Are you referring to dbisam server (dbsrvr) version difference (i.e.
client was compiled with 4.43b1 and dbsrvr was still 4.42b2) ?

The error you listed should not be caused by this either way.

4.43 does not have any major changes relative 4.42 IMHO - there is
Delphi Berlin support, runtime package output directory change and some
fixes but otherwise they should be compatible.

Raul

Hi Raul

Thank you for your response.

( so prior to issue my dev machine had 4.42 b2 and client had 4.43 b1 server

1. I just installed the latest version of dbisam server and utils and components on my machine.
( to match the version of dbsrvr on clients pc )
2. recompiled the app.
3. loaded to client machine.

The problem was solved.

Note sure why the version would have made a difference  .... but that worked for me.

Regards

Kamran

Raul wrote:

On 6/15/2016 7:52 AM, kamran wrote:
> Just in case anybody else has this issue.
> I just checked the versions of DBIsam on client and and my pc
> and there was a mismatch. of 4.42 b2 and 4.43 b1
> I have corrected this. And this seems to have done the trick.

Are you referring to dbisam server (dbsrvr) version difference (i.e.
client was compiled with 4.43b1 and dbsrvr was still 4.42b2) ?

The error you listed should not be caused by this either way.

4.43 does not have any major changes relative 4.42 IMHO - there is
Delphi Berlin support, runtime package output directory change and some
fixes but otherwise they should be compatible.

Raul