I have D4 and dbisam 2 working together, and I also have D6 and dbisam3
working with each other.

Is there any way I could have dbisam and D6 installed so that it could
access EITHER dbisam 2 or 3 (or 4 if I upgraded further)?  Or elevateDB?
 I dont want an app with more than one db in it, but I would like to be
able to work on older apps with the older database, and newer apps with
the newer one.

Jerry

Jerry,

DBISAM (either v2 or v3 or v4) and ElevateDB coexist on the same IDE
with no issues.

--
Regards,
Jan Ferguson


Jerry Blumenthal wrote:

<<I have D4 and dbisam 2 working together, and I also have D6 and
<<dbisam3 working with each other.
<<
<<Is there any way I could have dbisam and D6 installed so that it
<<could access EITHER dbisam 2 or 3 (or 4 if I upgraded further)?  Or
<<elevateDB?   I dont want an app with more than one db in it, but I
<<would like to be able to work on older apps with the older database,
<<and newer apps with the newer one.
<<
<<Jerry
>>

Jerry

Jerry


As Jan indicates DBISAM and ElevateDB are different and the component names are different so there's no problem in them co-existing.

DBISAM, however, in all its incarnations, has the same component names so its a bit more tricky. There is a utility which will allow you to save and load a Delphi configuration but as usual my memory doesn't have it stored. I know its been mentioned several times.

I knew there was one on the web so have a look at this  http://www.jed-software.com/product.htm

Roy Lambert

"Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
news:B327242B-A616-4DC5-AF73-DF9D97A658E9@news.elevatesoft.com...
>I have D4 and dbisam 2 working together, and I also have D6 and dbisam3
>working with each other.
>
> Is there any way I could have dbisam and D6 installed so that it could
> access EITHER dbisam 2 or 3 (or 4 if I upgraded further)?  Or elevateDB? I
> dont want an app with more than one db in it, but I would like to be able
> to work on older apps with the older database, and newer apps with the
> newer one.

Jerry,

I am curious what your specific situation is which requires not upgrading
certain applications to a newer version of DBISAM. I have a few thousand
users on DBISAM 4 right now, but I feel after ElevateDB is proven I will
make the effort to get everyone upgraded. Of course I have embedded
provisions for upgrading, but I feel using older libraries as always
contra-effective, almost as bad as adopting new technology without
significant proven reliability.

-Johnnie

Johnnie Norsworthy wrote:
> "Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
> news:B327242B-A616-4DC5-AF73-DF9D97A658E9@news.elevatesoft.com...
>> I have D4 and dbisam 2 working together, and I also have D6 and dbisam3
>> working with each other.
>>
>> Is there any way I could have dbisam and D6 installed so that it could
>> access EITHER dbisam 2 or 3 (or 4 if I upgraded further)?  Or elevateDB? I
>> dont want an app with more than one db in it, but I would like to be able
>> to work on older apps with the older database, and newer apps with the
>> newer one.
>
> Jerry,
>
> I am curious what your specific situation is which requires not upgrading
> certain applications to a newer version of DBISAM. I have a few thousand
> users on DBISAM 4 right now, but I feel after ElevateDB is proven I will
> make the effort to get everyone upgraded. Of course I have embedded
> provisions for upgrading, but I feel using older libraries as always
> contra-effective, almost as bad as adopting new technology without
> significant proven reliability.
>
> -Johnnie
>
>

Johnnie-

I am cheap and also lazy.  Wouldnt that just about cover it?

Also- my clientele does not upgrade.  The government has just come out
with new regulations that require changing of insurance claim forms, and
as a result I am selling a new version of my windows software.  Many of
the people who are upgrading to this new version have been using my DOS
version since 1991 and have been reluctant to change until forced to do so.

So my clientele is also cheap and lazy.  I probably need to learn
marketing strategies to "make the effort to get everyone upgraded"--- I
dont know how to do that.

Jerry

"Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
news:1F3B1516-BDF5-46B2-AA0C-78AAB34C6A51@news.elevatesoft.com...
>
> So my clientele is also cheap and lazy.  I probably need to learn
> marketing strategies to "make the effort to get everyone upgraded"--- I
> dont know how to do that.
>
Dear customer:
We are proud to announce the release of the new version of our product.These
are the reasons why you should upgrade: 1 2 and 3. The upgrade price is
$xxxx. PLEASE NOTE:  after xx/xx/xxxx we will discontinue support for
previous versions
Respectfully,
Attila

If someone does not want to upgrade, at least they don't waste your time
with maintenance issues (plus you could make money consulting on conversion
to a new program from someone else). I nobody wants to upgrade, you kill the
product and go to the beach. Life is too short to talk to "customers" who
don't make money for you.

Robert

It's a very simple concept that took me forever to learn and practice,
but it sure does cut through the crap--and it sure does work.

Once people understand you'll do everything for them for free, they'll
never let you go and they'll never pay a dime until they are forced.

Regards,

Jason Lee

Robert wrote:
> <snip> Life is too short to talk to "customers" who
> don't make money for you.

Robert wrote:
> "Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
> news:1F3B1516-BDF5-46B2-AA0C-78AAB34C6A51@news.elevatesoft.com...
>> So my clientele is also cheap and lazy.  I probably need to learn
>> marketing strategies to "make the effort to get everyone upgraded"--- I
>> dont know how to do that.
>>
> Dear customer:
> We are proud to announce the release of the new version of our product.These
> are the reasons why you should upgrade: 1 2 and 3. The upgrade price is
> $xxxx. PLEASE NOTE:  after xx/xx/xxxx we will discontinue support for
> previous versions
> Respectfully,
> Attila
>
> If someone does not want to upgrade, at least they don't waste your time
> with maintenance issues (plus you could make money consulting on conversion
> to a new program from someone else). I nobody wants to upgrade, you kill the
> product and go to the beach. Life is too short to talk to "customers" who
> don't make money for you.
>
> Robert
>
>

My cousin, who was the cfo and then the ceo of a fortune 500 company,
agrees with you, and yells at me for not doing just that.  I know you're
right, but.....
Jerry

Jerry,

<< I am cheap and also lazy.  Wouldnt that just about cover it? >>

Major points for honesty.   Actually, I can understand not wanting to
rock the boat - I try to keep our internal stuff running as long as possible
without changes.  Every day that it runs without a change is another day
where it is paying back what it cost to develop.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Jerry Blumenthal" <jerry@blumenthalsoftware.com> wrote in message
news:1F3B1516-BDF5-46B2-AA0C-78AAB34C6A51@news.elevatesoft.com...

> Also- my clientele does not upgrade.  The government has just come out
> with new regulations that require changing of insurance claim forms, and
> as a result I am selling a new version of my windows software.  Many of
> the people who are upgrading to this new version have been using my DOS
> version since 1991 and have been reluctant to change until forced to do
> so.

I'm going to drop a bomb on my customers soon. No mo' Win95/98/ME. Wish me
luck!

-Johnnie