I'm a relatively new developer, and I've written a neat little database in
Access 2003. I'm starting to distribute it now, and it works great with
Windows XP, but I'm getting requests to produce a version that will work on
Windows 98.

If I could track down a copy of Access 2000 with the developer's
extensions/toolkit, would I be able to create a distributable package that
would work on the earlier platform?

I know I'd have to make some code modifications to make sure my db would
function in the earlier Access version, but other than that, would it work?

If not, any other suggestions? I've already looked at SageKey, but I'm not
able to spend $500 for an already outdated software package. I was hoping I
could find something on eBay or the like!

Thanks for your help!
Joe

Were it I, I would recommend those with '98 spend a few bucks and upgrade. I
really don't think it is worth your time and expense to mess around with an
operating system that is 3 or 4 versions out of date.

"J Holtendehouzer" wrote:

> I'm a relatively new developer, and I've written a neat little database in
> Access 2003. I'm starting to distribute it now, and it works great with
> Windows XP, but I'm getting requests to produce a version that will work on
> Windows 98.
>
> If I could track down a copy of Access 2000 with the developer's
> extensions/toolkit, would I be able to create a distributable package that
> would work on the earlier platform?
>
> I know I'd have to make some code modifications to make sure my db would
> function in the earlier Access version, but other than that, would it work?
>
> If not, any other suggestions? I've already looked at SageKey, but I'm not
> able to spend $500 for an already outdated software package. I was hoping I
> could find something on eBay or the like!
>
> Thanks for your help!
> Joe
>
>
>

I agree with you, but that's not my call. I'm selling to small businesses
who are reluctant to upgrade 10-20 computers at a time.

My problem is: Is there a way that I can inexpensively produce a compatible
product for them?

Thanks!
Joe

"Klatuu" <(E-Mail Removed)> wrote in message
news:16C71011-9803-47A7-96EB-(E-Mail Removed)...
> Were it I, I would recommend those with '98 spend a few bucks and upgrade.
> I
> really don't think it is worth your time and expense to mess around with
> an
> operating system that is 3 or 4 versions out of date.
>
> "J Holtendehouzer" wrote:
>
>> I'm a relatively new developer, and I've written a neat little database
>> in
>> Access 2003. I'm starting to distribute it now, and it works great with
>> Windows XP, but I'm getting requests to produce a version that will work
>> on
>> Windows 98.
>>
>> If I could track down a copy of Access 2000 with the developer's
>> extensions/toolkit, would I be able to create a distributable package
>> that
>> would work on the earlier platform?
>>
>> I know I'd have to make some code modifications to make sure my db would
>> function in the earlier Access version, but other than that, would it
>> work?
>>
>> If not, any other suggestions? I've already looked at SageKey, but I'm
>> not
>> able to spend $500 for an already outdated software package. I was
>> hoping I
>> could find something on eBay or the like!
>>
>> Thanks for your help!
>> Joe
>>
>>
>>

"J Holtendehouzer" <(E-Mail Removed)> wrote in message
news:BS46g.72373$(E-Mail Removed)...
> I'm a relatively new developer, and I've written a neat little database in
> Access 2003. I'm starting to distribute it now, and it works great with
> Windows XP, but I'm getting requests to produce a version that will work
> on Windows 98.
>
> If I could track down a copy of Access 2000 with the developer's
> extensions/toolkit, would I be able to create a distributable package that
> would work on the earlier platform?

Yes, but why not use office xp (access 2002). That was the last version that
worked on windows 98..

>
> I know I'd have to make some code modifications to make sure my db would
> function in the earlier Access version, but other than that, would it
> work?

Yes, for the most part it should work. You would simply convert the mdb to
a2000 format (note that the default format for a2003 is in fact a2000 -- you
might be already using a2000 format. However, if you created a a2003
mde..then you had to have changed your format to 2002/2003 format anyway.)

>
> If not, any other suggestions? I've already looked at SageKey

Sagekey does not provide the runtime, so, they are no help in this case
(note sure why you brought them up). You certainly could switch to a2002,
and
thus your runtime would work with win98 to the current system.

You can use sagekey to build a install here...but sagkey changes nothing in
terms of what version of windows you can install on. Sagkey only provides
the install scripts, you still have to have purchased the appropriate
runtime
and ms-access developers tools. So, sagekey only provides a install script,
(and, optionally will sell a installer). However, in all cases, you have
to provide/own the runtimes. You can also use the windows installer, and
thus save the cost of purchasing a installer such as InstallSheild or Wise.
Last time I looked, a2003 scripts were a very reasonable $500

Anyway, a2002 does run on all win98SE to present. I don't think a2002 works
on
windows 95 however (can't remember). So, do you need windows 95 also?
That issue would force
you back to a2000 in place of a2002 as a better choice. In fact, if you need
win95, then why not choose access97, as it is a MUCH better choice then
a2000. The runtime for a2000 was 150 megs in size, and for access97, it was
about 13 megs in size. And, for a2003, it is about 33 megs.

So, I would go all the way back to a97 if I was looking to support win95,
and win98. If you can live with win98SE, then I would perhaps choose a2002,
as this will install on all versions from win98SE to present versions.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)
http://www.members.shaw.ca/AlbertKallal

OK-That's reasonable. I didn't realize a2002 would run on Win98SE. I'm
currently running a2003; I assume that just converting the database itself
to a2002 won't change the runtime that gets packaged with it.

I still have my old copy of Office XP, but I don't have any developer
extensions or toolkits. If office 2003 developers extensions doesn't
include the 2002 runtime, any idea where I could get it?

You've been very helpful--thanks!
Joe


"Albert D.Kallal" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "J Holtendehouzer" <(E-Mail Removed)> wrote in message
> news:BS46g.72373$(E-Mail Removed)...
>> I'm a relatively new developer, and I've written a neat little database
>> in
>> Access 2003. I'm starting to distribute it now, and it works great with
>> Windows XP, but I'm getting requests to produce a version that will work
>> on Windows 98.
>>
>> If I could track down a copy of Access 2000 with the developer's
>> extensions/toolkit, would I be able to create a distributable package
>> that
>> would work on the earlier platform?
>
> Yes, but why not use office xp (access 2002). That was the last version
> that
> worked on windows 98..
>
>>
>> I know I'd have to make some code modifications to make sure my db would
>> function in the earlier Access version, but other than that, would it
>> work?
>
> Yes, for the most part it should work. You would simply convert the mdb to
> a2000 format (note that the default format for a2003 is in fact a2000 --
> you
> might be already using a2000 format. However, if you created a a2003
> mde..then you had to have changed your format to 2002/2003 format anyway.)
>
>>
>> If not, any other suggestions? I've already looked at SageKey
>
> Sagekey does not provide the runtime, so, they are no help in this case
> (note sure why you brought them up). You certainly could switch to a2002,
> and
> thus your runtime would work with win98 to the current system.
>
> You can use sagekey to build a install here...but sagkey changes nothing
> in
> terms of what version of windows you can install on. Sagkey only provides
> the install scripts, you still have to have purchased the appropriate
> runtime
> and ms-access developers tools. So, sagekey only provides a install
> script,
> (and, optionally will sell a installer). However, in all cases, you have
> to provide/own the runtimes. You can also use the windows installer, and
> thus save the cost of purchasing a installer such as InstallSheild or
> Wise.
> Last time I looked, a2003 scripts were a very reasonable $500
>
> Anyway, a2002 does run on all win98SE to present. I don't think a2002
> works on
> windows 95 however (can't remember). So, do you need windows 95 also?
> That issue would force
> you back to a2000 in place of a2002 as a better choice. In fact, if you
> need
> win95, then why not choose access97, as it is a MUCH better choice then
> a2000. The runtime for a2000 was 150 megs in size, and for access97, it
> was
> about 13 megs in size. And, for a2003, it is about 33 megs.
>
> So, I would go all the way back to a97 if I was looking to support win95,
> and win98. If you can live with win98SE, then I would perhaps choose
> a2002,
> as this will install on all versions from win98SE to present versions.
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> (E-Mail Removed)
> http://www.members.shaw.ca/AlbertKallal
>
>
>

Office 2003 developers extensions do not include the 2002 runtime and,
unfortunately, Microsoft no longer sells previous versions of Access.

One possibility is to check out sites that specialize in old software
products, such as http://www.emsps.com/oldtools/ or
http://recycledsoftware.com/

Another is to look at someplace like eBay to see whether anyone's trying to
sell their old versions (Note, though, that products purchased this way
aren't always legal...)


--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"J Holtendehouzer" <(E-Mail Removed)> wrote in message
news:i296g.67170$(E-Mail Removed)...
> OK-That's reasonable. I didn't realize a2002 would run on Win98SE. I'm
> currently running a2003; I assume that just converting the database itself
> to a2002 won't change the runtime that gets packaged with it.
>
> I still have my old copy of Office XP, but I don't have any developer
> extensions or toolkits. If office 2003 developers extensions doesn't
> include the 2002 runtime, any idea where I could get it?
>
> You've been very helpful--thanks!
> Joe
>
>
> "Albert D.Kallal" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> "J Holtendehouzer" <(E-Mail Removed)> wrote in message
>> news:BS46g.72373$(E-Mail Removed)...
>>> I'm a relatively new developer, and I've written a neat little database
>>> in
>>> Access 2003. I'm starting to distribute it now, and it works great with
>>> Windows XP, but I'm getting requests to produce a version that will work
>>> on Windows 98.
>>>
>>> If I could track down a copy of Access 2000 with the developer's
>>> extensions/toolkit, would I be able to create a distributable package
>>> that
>>> would work on the earlier platform?
>>
>> Yes, but why not use office xp (access 2002). That was the last version
>> that
>> worked on windows 98..
>>
>>>
>>> I know I'd have to make some code modifications to make sure my db would
>>> function in the earlier Access version, but other than that, would it
>>> work?
>>
>> Yes, for the most part it should work. You would simply convert the mdb
>> to
>> a2000 format (note that the default format for a2003 is in fact a2000 --
>> you
>> might be already using a2000 format. However, if you created a a2003
>> mde..then you had to have changed your format to 2002/2003 format
>> anyway.)
>>
>>>
>>> If not, any other suggestions? I've already looked at SageKey
>>
>> Sagekey does not provide the runtime, so, they are no help in this case
>> (note sure why you brought them up). You certainly could switch to a2002,
>> and
>> thus your runtime would work with win98 to the current system.
>>
>> You can use sagekey to build a install here...but sagkey changes nothing
>> in
>> terms of what version of windows you can install on. Sagkey only provides
>> the install scripts, you still have to have purchased the appropriate
>> runtime
>> and ms-access developers tools. So, sagekey only provides a install
>> script,
>> (and, optionally will sell a installer). However, in all cases, you have
>> to provide/own the runtimes. You can also use the windows installer, and
>> thus save the cost of purchasing a installer such as InstallSheild or
>> Wise.
>> Last time I looked, a2003 scripts were a very reasonable $500
>>
>> Anyway, a2002 does run on all win98SE to present. I don't think a2002
>> works on
>> windows 95 however (can't remember). So, do you need windows 95 also?
>> That issue would force
>> you back to a2000 in place of a2002 as a better choice. In fact, if you
>> need
>> win95, then why not choose access97, as it is a MUCH better choice then
>> a2000. The runtime for a2000 was 150 megs in size, and for access97, it
>> was
>> about 13 megs in size. And, for a2003, it is about 33 megs.
>>
>> So, I would go all the way back to a97 if I was looking to support win95,
>> and win98. If you can live with win98SE, then I would perhaps choose
>> a2002,
>> as this will install on all versions from win98SE to present versions.
>>
>>
>> --
>> Albert D. Kallal (Access MVP)
>> Edmonton, Alberta Canada
>> (E-Mail Removed)
>> http://www.members.shaw.ca/AlbertKallal
>>
>>
>>
>
>

> I still have my old copy of Office XP, but I don't have any developer
> extensions or toolkits. If office 2003 developers extensions doesn't
> include the 2002 runtime, any idea where I could get it?

Hum, I don't have a answer for that. (but, you are correct, that a2003
developers system
does not include previous versions such as a2002 runtime).

I suppose you could try some used software sites, or perhaps eBay...


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)
http://www.members.shaw.ca/AlbertKallal

Just to be clear, though, what I'm looking for is the Office 2002 (which is
the same as XP, correct?) Developer Edition. Is there a separate Access
2002 Developer's Edition, or does it only come as the suite?

I thank you again for your help,
Joe

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
news:%(E-Mail Removed)...
> Office 2003 developers extensions do not include the 2002 runtime and,
> unfortunately, Microsoft no longer sells previous versions of Access.
>
> One possibility is to check out sites that specialize in old software
> products, such as http://www.emsps.com/oldtools/ or
> http://recycledsoftware.com/
>
> Another is to look at someplace like eBay to see whether anyone's trying
> to sell their old versions (Note, though, that products purchased this way
> aren't always legal...)
>
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no private e-mails, please)
>
>
> "J Holtendehouzer" <(E-Mail Removed)> wrote in message
> news:i296g.67170$(E-Mail Removed)...
>> OK-That's reasonable. I didn't realize a2002 would run on Win98SE. I'm
>> currently running a2003; I assume that just converting the database
>> itself to a2002 won't change the runtime that gets packaged with it.
>>
>> I still have my old copy of Office XP, but I don't have any developer
>> extensions or toolkits. If office 2003 developers extensions doesn't
>> include the 2002 runtime, any idea where I could get it?
>>
>> You've been very helpful--thanks!
>> Joe
>>
>>
>> "Albert D.Kallal" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> "J Holtendehouzer" <(E-Mail Removed)> wrote in message
>>> news:BS46g.72373$(E-Mail Removed)...
>>>> I'm a relatively new developer, and I've written a neat little database
>>>> in
>>>> Access 2003. I'm starting to distribute it now, and it works great
>>>> with
>>>> Windows XP, but I'm getting requests to produce a version that will
>>>> work
>>>> on Windows 98.
>>>>
>>>> If I could track down a copy of Access 2000 with the developer's
>>>> extensions/toolkit, would I be able to create a distributable package
>>>> that
>>>> would work on the earlier platform?
>>>
>>> Yes, but why not use office xp (access 2002). That was the last version
>>> that
>>> worked on windows 98..
>>>
>>>>
>>>> I know I'd have to make some code modifications to make sure my db
>>>> would
>>>> function in the earlier Access version, but other than that, would it
>>>> work?
>>>
>>> Yes, for the most part it should work. You would simply convert the mdb
>>> to
>>> a2000 format (note that the default format for a2003 is in fact a2000 --
>>> you
>>> might be already using a2000 format. However, if you created a a2003
>>> mde..then you had to have changed your format to 2002/2003 format
>>> anyway.)
>>>
>>>>
>>>> If not, any other suggestions? I've already looked at SageKey
>>>
>>> Sagekey does not provide the runtime, so, they are no help in this case
>>> (note sure why you brought them up). You certainly could switch to
>>> a2002, and
>>> thus your runtime would work with win98 to the current system.
>>>
>>> You can use sagekey to build a install here...but sagkey changes nothing
>>> in
>>> terms of what version of windows you can install on. Sagkey only
>>> provides
>>> the install scripts, you still have to have purchased the appropriate
>>> runtime
>>> and ms-access developers tools. So, sagekey only provides a install
>>> script,
>>> (and, optionally will sell a installer). However, in all cases, you have
>>> to provide/own the runtimes. You can also use the windows installer, and
>>> thus save the cost of purchasing a installer such as InstallSheild or
>>> Wise.
>>> Last time I looked, a2003 scripts were a very reasonable $500
>>>
>>> Anyway, a2002 does run on all win98SE to present. I don't think a2002
>>> works on
>>> windows 95 however (can't remember). So, do you need windows 95 also?
>>> That issue would force
>>> you back to a2000 in place of a2002 as a better choice. In fact, if you
>>> need
>>> win95, then why not choose access97, as it is a MUCH better choice then
>>> a2000. The runtime for a2000 was 150 megs in size, and for access97, it
>>> was
>>> about 13 megs in size. And, for a2003, it is about 33 megs.
>>>
>>> So, I would go all the way back to a97 if I was looking to support
>>> win95,
>>> and win98. If you can live with win98SE, then I would perhaps choose
>>> a2002,
>>> as this will install on all versions from win98SE to present versions.
>>>
>>>
>>> --
>>> Albert D. Kallal (Access MVP)
>>> Edmonton, Alberta Canada
>>> (E-Mail Removed)
>>> http://www.members.shaw.ca/AlbertKallal
>>>
>>>
>>>
>>
>>
>
>

Realistically, there was no Access XP. There was Office XP, which contained
Access 2002, Excel 2002, PowerPoint 2002, Word 2002 and so on. (picky, I
know...)

There's definitely no such thing as Access 2002 Developer's Edition: the
only thing there was was Office XP Developer. In fact, I don't believe you
can get just the Developer Edition for Office XP, like you could for Office
2000. I believe Office XP Developer will be a complete copy of Office XP
Professional, plus the Office XP Developer Edition (which implies a higher
cost)

Tony Toews has an overview of all this stuff at
http://www.granite.ab.ca/access/deve...onversions.htm

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"J Holtendehouzer" <(E-Mail Removed)> wrote in message
news:Qpm6g.21765$(E-Mail Removed)...
> Just to be clear, though, what I'm looking for is the Office 2002 (which
is
> the same as XP, correct?) Developer Edition. Is there a separate Access
> 2002 Developer's Edition, or does it only come as the suite?
>
> I thank you again for your help,
> Joe
>
> "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
> news:%(E-Mail Removed)...
> > Office 2003 developers extensions do not include the 2002 runtime and,
> > unfortunately, Microsoft no longer sells previous versions of Access.
> >
> > One possibility is to check out sites that specialize in old software
> > products, such as http://www.emsps.com/oldtools/ or
> > http://recycledsoftware.com/
> >
> > Another is to look at someplace like eBay to see whether anyone's trying
> > to sell their old versions (Note, though, that products purchased this
way
> > aren't always legal...)
> >
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no private e-mails, please)
> >
> >
> > "J Holtendehouzer" <(E-Mail Removed)> wrote in message
> > news:i296g.67170$(E-Mail Removed)...
> >> OK-That's reasonable. I didn't realize a2002 would run on Win98SE.
I'm
> >> currently running a2003; I assume that just converting the database
> >> itself to a2002 won't change the runtime that gets packaged with it.
> >>
> >> I still have my old copy of Office XP, but I don't have any developer
> >> extensions or toolkits. If office 2003 developers extensions doesn't
> >> include the 2002 runtime, any idea where I could get it?
> >>
> >> You've been very helpful--thanks!
> >> Joe
> >>
> >>
> >> "Albert D.Kallal" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>> "J Holtendehouzer" <(E-Mail Removed)> wrote in message
> >>> news:BS46g.72373$(E-Mail Removed)...
> >>>> I'm a relatively new developer, and I've written a neat little
database
> >>>> in
> >>>> Access 2003. I'm starting to distribute it now, and it works great
> >>>> with
> >>>> Windows XP, but I'm getting requests to produce a version that will
> >>>> work
> >>>> on Windows 98.
> >>>>
> >>>> If I could track down a copy of Access 2000 with the developer's
> >>>> extensions/toolkit, would I be able to create a distributable package
> >>>> that
> >>>> would work on the earlier platform?
> >>>
> >>> Yes, but why not use office xp (access 2002). That was the last
version
> >>> that
> >>> worked on windows 98..
> >>>
> >>>>
> >>>> I know I'd have to make some code modifications to make sure my db
> >>>> would
> >>>> function in the earlier Access version, but other than that, would it
> >>>> work?
> >>>
> >>> Yes, for the most part it should work. You would simply convert the
mdb
> >>> to
> >>> a2000 format (note that the default format for a2003 is in fact
a2000 --
> >>> you
> >>> might be already using a2000 format. However, if you created a a2003
> >>> mde..then you had to have changed your format to 2002/2003 format
> >>> anyway.)
> >>>
> >>>>
> >>>> If not, any other suggestions? I've already looked at SageKey
> >>>
> >>> Sagekey does not provide the runtime, so, they are no help in this
case
> >>> (note sure why you brought them up). You certainly could switch to
> >>> a2002, and
> >>> thus your runtime would work with win98 to the current system.
> >>>
> >>> You can use sagekey to build a install here...but sagkey changes
nothing
> >>> in
> >>> terms of what version of windows you can install on. Sagkey only
> >>> provides
> >>> the install scripts, you still have to have purchased the appropriate
> >>> runtime
> >>> and ms-access developers tools. So, sagekey only provides a install
> >>> script,
> >>> (and, optionally will sell a installer). However, in all cases, you
have
> >>> to provide/own the runtimes. You can also use the windows installer,
and
> >>> thus save the cost of purchasing a installer such as InstallSheild or
> >>> Wise.
> >>> Last time I looked, a2003 scripts were a very reasonable $500
> >>>
> >>> Anyway, a2002 does run on all win98SE to present. I don't think a2002
> >>> works on
> >>> windows 95 however (can't remember). So, do you need windows 95 also?
> >>> That issue would force
> >>> you back to a2000 in place of a2002 as a better choice. In fact, if
you
> >>> need
> >>> win95, then why not choose access97, as it is a MUCH better choice
then
> >>> a2000. The runtime for a2000 was 150 megs in size, and for access97,
it
> >>> was
> >>> about 13 megs in size. And, for a2003, it is about 33 megs.
> >>>
> >>> So, I would go all the way back to a97 if I was looking to support
> >>> win95,
> >>> and win98. If you can live with win98SE, then I would perhaps choose
> >>> a2002,
> >>> as this will install on all versions from win98SE to present versions.
> >>>
> >>>
> >>> --
> >>> Albert D. Kallal (Access MVP)
> >>> Edmonton, Alberta Canada
> >>> (E-Mail Removed)
> >>> http://www.members.shaw.ca/AlbertKallal
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>

Some of these people might already have Office Pro/Access installed.
All you would have to do is provide the application files and perhaps
shortcuts.

We have the A97 runtime licence, but we don't provide it anymore:
any client who is still running Office 97 supplies their own copy.
Some of these people are running A97 retail, and some have copies
of the A97 runtime that is associated with some other application.

At minimum, you need to consider what fraction of your Win98
clients already have a version of Access installed, before you worry
about providing runtime copies.

(david)


"J Holtendehouzer" <(E-Mail Removed)> wrote in message
news:Px66g.1126$(E-Mail Removed)...
> I agree with you, but that's not my call. I'm selling to small businesses
> who are reluctant to upgrade 10-20 computers at a time.
>
> My problem is: Is there a way that I can inexpensively produce a
compatible
> product for them?
>
> Thanks!
> Joe
>
> "Klatuu" <(E-Mail Removed)> wrote in message
> news:16C71011-9803-47A7-96EB-(E-Mail Removed)...
> > Were it I, I would recommend those with '98 spend a few bucks and
upgrade.
> > I
> > really don't think it is worth your time and expense to mess around with
> > an
> > operating system that is 3 or 4 versions out of date.
> >
> > "J Holtendehouzer" wrote:
> >
> >> I'm a relatively new developer, and I've written a neat little database
> >> in
> >> Access 2003. I'm starting to distribute it now, and it works great
with
> >> Windows XP, but I'm getting requests to produce a version that will
work
> >> on
> >> Windows 98.
> >>
> >> If I could track down a copy of Access 2000 with the developer's
> >> extensions/toolkit, would I be able to create a distributable package
> >> that
> >> would work on the earlier platform?
> >>
> >> I know I'd have to make some code modifications to make sure my db
would
> >> function in the earlier Access version, but other than that, would it
> >> work?
> >>
> >> If not, any other suggestions? I've already looked at SageKey, but I'm
> >> not
> >> able to spend $500 for an already outdated software package. I was
> >> hoping I
> >> could find something on eBay or the like!
> >>
> >> Thanks for your help!
> >> Joe
> >>
> >>
> >>
>
>