Hello everyone,
I guess I should've posted this under Third Party Job Postings but it seems pretty much dead and full of spam so I decided to post it here instead.
I'm going to covert another BDE/Paradox based application into DBISAM and I'd like to add a new feature that would allow the users to connect to the database locally or over the Internet using client/server
mode. I know DBISAM can handle this and by spending some time reading the manual, this newsgroup and doing some tests I can make it work. However, since I haven't done this before I would much prefer
to get a time tested code that I'm sure some of you have developed to use in your own projects. What I need is a sample project that will load configuration information from an ini file at startup and try to
create the data module and connect to the database locally or over the internet by properly handling all the steps necessary and outputting meaningfull error message in case of problems (missing database
files, no internet connection, no server and so on).
On the data module I'd like to see a sample table and query components that handle data updates in the best possible way - I want to create the data module from scratch instead of simply converting the
existing bde datamodule to make sure everything is done according to dbisam best practices.
If you're interested, please send an email with a rough estimate to garikmm at gmail dot com.
Thanks,

Garik

Garik wrote:

> If you're interested,
> please send an email with a rough estimate to garikmm at gmail dot
> com.  Thanks,
>
> Garik

Try Context Extensions.  The included OpenDbisamDlg already handles
this.

--

Thank David for the suggestion. I installed the trial version to see how it works and run into some problems trying to use the component you've mentioned. I get exceptions every time I
try to switch between local and server modes and the databases list is not showing the databases I've setup while I can see them when I'm using dbsys in remote mode.
I'll give it another try when I have some time.
Regards,

Garik


"David Farrell-Garcia" <davidF@WhidbeyIslandSoftware.com> wrote:

Garik wrote:

> If you're interested,
> please send an email with a rough estimate to garikmm at gmail dot
> com.  Thanks,
>
> Garik

Try Context Extensions.  The included OpenDbisamDlg already handles
this.

--

Garik M wrote:

> Thank David for the suggestion. I installed the trial version to see
> how it works and run into some problems trying to use the component
> you've mentioned. I get exceptions every time I try to switch between
> local and server modes



I am using Context Extensions 2.02 but I think the DbisamOpenDialog is
the same as the earlier version. It works perfect for me for both
local, WAN and Internet connections. If you are having a specfic
problem email Michael. His support is superb.

I just came accross this same problem only a couple of days ago.  I think
maybe an older version of DBISAMOpenDatabase.pas has shipped with the latest
beta.

There is a line missing in the LoadDatabases procedure to open the session
before getting the remote database names.
try

DBISAMSession.Active := True;   ********Missing Line********

DBISAMSession.GetRemoteDatabaseNames(Items);

except

// We don't care about exceptions here

end;

Michael (Context Software) is aware of it.
--
Gavin Horne
www.hornesoftware.com.au


"David Farrell-Garcia" <davidF@WhidbeyIslandSoftware.com> wrote in message
news:E50B252F-BF15-4489-AB98-28D8F5B23FC1@news.elevatesoft.com...
> Garik M wrote:
>
>> Thank David for the suggestion. I installed the trial version to see
>> how it works and run into some problems trying to use the component
>> you've mentioned. I get exceptions every time I try to switch between
>> local and server modes
>
>
>
> I am using Context Extensions 2.02 but I think the DbisamOpenDialog is
> the same as the earlier version. It works perfect for me for both
> local, WAN and Internet connections. If you are having a specfic
> problem email Michael. His support is superb.

Hi Garik,

Please, see Gavin's post below - his suggestion is correct.
Somehow, although this is an old problem and has been fixed
many months ago, it appeared, that 2.02 was shipped with a
wrong version of DBISAMOpenDatabase.pas. The correct
version should read exactly as Gavin suggests:

try
  DBISAMSession.Active := True;   ********Missing Line********
  DBISAMSession.GetRemoteDatabaseNames(Items);
except
  // We don't care about exceptions here
end;

Please, correct the error in code and I will make sure the next
release is shipped with the correct version of this file.

Sorry about this.

Sincerely,
Michael

Garik M wrote:
> Thank David for the suggestion. I installed the trial version to see how it works and run into some problems trying to use the component you've mentioned. I get exceptions every time I
> try to switch between local and server modes and the databases list is not showing the databases I've setup while I can see them when I'm using dbsys in remote mode.
> I'll give it another try when I have some time.
> Regards,
>
> Garik
>
>
> "David Farrell-Garcia" <davidF@WhidbeyIslandSoftware.com> wrote:
>
> Garik wrote:
>
>> If you're interested,
>> please send an email with a rough estimate to garikmm at gmail dot
>> com.  Thanks,
>>
>> Garik
>
> Try Context Extensions.  The included OpenDbisamDlg already handles
> this.
>

Hello Michael,
Is this the only line missing in version 2.02?
And every time there's a new update available for DBISAM, should I wait for an update from you in order to update DBISAM or it's not necessary?
I noticed several incompatibility issues with DBISAM versions in your product's version history.
Regards,

Garik




Michael Baytalsky <mike@contextsoft.com> wrote:

Hi Garik,

Please, see Gavin's post below - his suggestion is correct.
Somehow, although this is an old problem and has been fixed
many months ago, it appeared, that 2.02 was shipped with a
wrong version of DBISAMOpenDatabase.pas. The correct
version should read exactly as Gavin suggests:

try
  DBISAMSession.Active := True;   ********Missing Line********
  DBISAMSession.GetRemoteDatabaseNames(Items);
except
  // We don't care about exceptions here
end;

Please, correct the error in code and I will make sure the next
release is shipped with the correct version of this file.

Sorry about this.

Sincerely,
Michael

Hello Garik,

> Is this the only line missing in version 2.02?
I certainly hope so

> And every time there's a new update available for DBISAM, should I wait for
> an update from you in order to update DBISAM or it's not necessary? I noticed
> several incompatibility issues with DBISAM versions in your product's version
> history.
Well, generally, it's not necessary, although these things happen in
past, but mostly around the transition between dbisam 3 and 4. Dbisam's
interfaces are quite stable now, so I don't think anything should change
anymore as far as v.4 concerned.

Regards,
Michael

>
>
>
>
> Michael Baytalsky <mike@contextsoft.com> wrote:
>
> Hi Garik,
>
> Please, see Gavin's post below - his suggestion is correct.
> Somehow, although this is an old problem and has been fixed
> many months ago, it appeared, that 2.02 was shipped with a
> wrong version of DBISAMOpenDatabase.pas. The correct
> version should read exactly as Gavin suggests:
>
> try
>    DBISAMSession.Active := True;   ********Missing Line********
>    DBISAMSession.GetRemoteDatabaseNames(Items);
> except
>    // We don't care about exceptions here
> end;
>
> Please, correct the error in code and I will make sure the next
> release is shipped with the correct version of this file.
>
> Sorry about this.
>
> Sincerely,
> Michael
>

Michael Baytalsky wrote:

> Hi Garik,
>
> Please, see Gavin's post below - his suggestion is correct.
> Somehow, although this is an old problem and has been fixed
> many months ago, it appeared, that 2.02 was shipped with a
> wrong version of DBISAMOpenDatabase.pas. The correct
> version should read exactly as Gavin suggests:


hmmm.  My copy already has that line.  IIRC I think that I discovered
this early on.