I have developed an application in Excel 2002 and they have now decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi version
option from the SaveAs dialog - It tries to save it - gets to 16k - pauses
for ages (20+mins) - then tells me "Document not saved" without a reason.
The first time it did tell me that I would have to change the protection on
the VBA code, which I did, as a project which is protected for viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.

I would normally not create something in XP which needed to be
used in 2000 BUT the decision to not upgrade all computers was
not made until after I finished the application. You have to love
moving goal posts.

I have tried to save the workbook as a multi version workbook from
XP but it gets to 16k saved, waits for ages (20 + mins) then tells me
it is not saved, and it is not saved. I have saved it as a multi version
workbook from 2000 and it appears to work with a few minor
changes but I need to test it fully.

Chrissy.


Bernie Deitrick wrote
Chrissy,

It is always better to develop in the lowest version that your application will be used with. I think that there is no difference
to the file structure, so try simply saving your file as a regular workbook.

Visit

http://msdn.microsoft.com/library/de...texcel2000.asp

for a listing of things that were new to XP, so that you can avoid using them in your application.

HTH,
Bernie
Excel MVP


"Chrissy" wrote in message ...
I have developed an application in Excel 2002 and they have now decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi version
option from the SaveAs dialog - It tries to save it - gets to 16k - pauses
for ages (20+mins) - then tells me "Document not saved" without a reason.
The first time it did tell me that I would have to change the protection on
the VBA code, which I did, as a project which is protected for viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.

Hi Chrissy -

Your efforts at this time should include running your workbook in Excel
2000 to see where it might fall down. How are you saving the workbook
as multi version? The file structure between '97 and XP is unchanged,
and the multi version workbooks I know of save both this workbook and an
Excel 95 workbook in the same file, at twice the disk space.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
http://www.geocities.com/jonpeltier/Excel/index.html
_______

Chrissy wrote:
I would normally not create something in XP which needed to be
used in 2000 BUT the decision to not upgrade all computers was
not made until after I finished the application. You have to love
moving goal posts.

I have tried to save the workbook as a multi version workbook from
XP but it gets to 16k saved, waits for ages (20 + mins) then tells me
it is not saved, and it is not saved. I have saved it as a multi version
workbook from 2000 and it appears to work with a few minor
changes but I need to test it fully.

Chrissy.


Bernie Deitrick wrote

Chrissy,

It is always better to develop in the lowest version that your application will be used with. I think that there is no difference
to the file structure, so try simply saving your file as a regular workbook.

Visit

http://msdn.microsoft.com/library/de...texcel2000.asp

for a listing of things that were new to XP, so that you can avoid using them in your application.

HTH,
Bernie
Excel MVP


"Chrissy" wrote in message ...

I have developed an application in Excel 2002 and they have now decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi version
option from the SaveAs dialog - It tries to save it - gets to 16k - pauses
for ages (20+mins) - then tells me "Document not saved" without a reason.
The first time it did tell me that I would have to change the protection on
the VBA code, which I did, as a project which is protected for viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.

I am saying that I am not prepared to say the application will work
unless I test it in 2000.

To save it was a multi version from 2002 I am choosing SaveAs and
selecting the Excel 97-2002 & 5.0/95 workbook. Are you saying that
this is not necessary?

So far the sort command does not work (had to change it to make it
work) and the Calendar control had to be replaced. There may be
other things but I will not know about them until I test.

Chrissy.

Jon Peltier wrote
Hi Chrissy -

Your efforts at this time should include running your workbook in Excel
2000 to see where it might fall down. How are you saving the workbook
as multi version? The file structure between '97 and XP is unchanged,
and the multi version workbooks I know of save both this workbook and an
Excel 95 workbook in the same file, at twice the disk space.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
http://www.geocities.com/jonpeltier/Excel/index.html
_______

Chrissy wrote:
I would normally not create something in XP which needed to be
used in 2000 BUT the decision to not upgrade all computers was
not made until after I finished the application. You have to love
moving goal posts.

I have tried to save the workbook as a multi version workbook from
XP but it gets to 16k saved, waits for ages (20 + mins) then tells me
it is not saved, and it is not saved. I have saved it as a multi version
workbook from 2000 and it appears to work with a few minor
changes but I need to test it fully.

Chrissy.


Bernie Deitrick wrote

Chrissy,

It is always better to develop in the lowest version that your application will be used with. I think that there is no
difference
to the file structure, so try simply saving your file as a regular workbook.

Visit

http://msdn.microsoft.com/library/de...texcel2000.asp

for a listing of things that were new to XP, so that you can avoid using them in your application.

HTH,
Bernie
Excel MVP


"Chrissy" wrote in message ...

I have developed an application in Excel 2002 and they have now decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi version
option from the SaveAs dialog - It tries to save it - gets to 16k - pauses
for ages (20+mins) - then tells me "Document not saved" without a reason.
The first time it did tell me that I would have to change the protection on
the VBA code, which I did, as a project which is protected for viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.

With reference to Windows Excel file formats:
Since VBA was introduced, there are only two Excel file formats. xl5/95 and
xl97-2002. So if you save normally in xl97, xl2000 or xl2002, you will save
in a file format that can be read by all three of those. No, you don't need
to use the combined Excel 97-2002 & 5.0/95 format.


--
Regards,
Tom Ogilvy

Chrissy wrote in message
...
I am saying that I am not prepared to say the application will work
unless I test it in 2000.

To save it was a multi version from 2002 I am choosing SaveAs and
selecting the Excel 97-2002 & 5.0/95 workbook. Are you saying that
this is not necessary?

So far the sort command does not work (had to change it to make it
work) and the Calendar control had to be replaced. There may be
other things but I will not know about them until I test.

Chrissy.

Jon Peltier wrote
Hi Chrissy -

Your efforts at this time should include running your workbook in Excel
2000 to see where it might fall down. How are you saving the workbook
as multi version? The file structure between '97 and XP is unchanged,
and the multi version workbooks I know of save both this workbook and an
Excel 95 workbook in the same file, at twice the disk space.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
http://www.geocities.com/jonpeltier/Excel/index.html
_______

Chrissy wrote:
I would normally not create something in XP which needed to be
used in 2000 BUT the decision to not upgrade all computers was
not made until after I finished the application. You have to love
moving goal posts.

I have tried to save the workbook as a multi version workbook from
XP but it gets to 16k saved, waits for ages (20 + mins) then tells me
it is not saved, and it is not saved. I have saved it as a multi
version
workbook from 2000 and it appears to work with a few minor
changes but I need to test it fully.

Chrissy.


Bernie Deitrick wrote

Chrissy,

It is always better to develop in the lowest version that your
application will be used with. I think that there is no
difference
to the file structure, so try simply saving your file as a regular
workbook.

Visit


http://msdn.microsoft.com/library/de...n-us/odeomg/ht
ml/deovrmicrosoftexcel2000.asp

for a listing of things that were new to XP, so that you can avoid
using them in your application.

HTH,
Bernie
Excel MVP


"Chrissy" wrote in message
...

I have developed an application in Excel 2002 and they have now
decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on
it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi
version
option from the SaveAs dialog - It tries to save it - gets to 16k -
pauses
for ages (20+mins) - then tells me "Document not saved" without a
reason.
The first time it did tell me that I would have to change the
protection on
the VBA code, which I did, as a project which is protected for
viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine
except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.

Thanks.

I did assume that saving in a diff version would also check the code for
compliance but I now realize that it does not.

Chrissy.

"Tom Ogilvy" wrote in message ...
With reference to Windows Excel file formats:
Since VBA was introduced, there are only two Excel file formats. xl5/95 and
xl97-2002. So if you save normally in xl97, xl2000 or xl2002, you will save
in a file format that can be read by all three of those. No, you don't need
to use the combined Excel 97-2002 & 5.0/95 format.


--
Regards,
Tom Ogilvy

Chrissy wrote in message
...
I am saying that I am not prepared to say the application will work
unless I test it in 2000.

To save it was a multi version from 2002 I am choosing SaveAs and
selecting the Excel 97-2002 & 5.0/95 workbook. Are you saying that
this is not necessary?

So far the sort command does not work (had to change it to make it
work) and the Calendar control had to be replaced. There may be
other things but I will not know about them until I test.

Chrissy.

Jon Peltier wrote
Hi Chrissy -

Your efforts at this time should include running your workbook in Excel
2000 to see where it might fall down. How are you saving the workbook
as multi version? The file structure between '97 and XP is unchanged,
and the multi version workbooks I know of save both this workbook and an
Excel 95 workbook in the same file, at twice the disk space.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
http://www.geocities.com/jonpeltier/Excel/index.html
_______

Chrissy wrote:
I would normally not create something in XP which needed to be
used in 2000 BUT the decision to not upgrade all computers was
not made until after I finished the application. You have to love
moving goal posts.

I have tried to save the workbook as a multi version workbook from
XP but it gets to 16k saved, waits for ages (20 + mins) then tells me
it is not saved, and it is not saved. I have saved it as a multi
version
workbook from 2000 and it appears to work with a few minor
changes but I need to test it fully.

Chrissy.


Bernie Deitrick wrote

Chrissy,

It is always better to develop in the lowest version that your
application will be used with. I think that there is no
difference
to the file structure, so try simply saving your file as a regular
workbook.

Visit


http://msdn.microsoft.com/library/de...n-us/odeomg/ht
ml/deovrmicrosoftexcel2000.asp

for a listing of things that were new to XP, so that you can avoid
using them in your application.

HTH,
Bernie
Excel MVP


"Chrissy" wrote in message
...

I have developed an application in Excel 2002 and they have now
decided
that they want it to run in Excel 2000.

What issues are likely to arise?

Is there any way I can work on the app on my PC, which has 2002 on
it,
and know that it will run on 2000 with out problems?

Is there a list of compatibility issues between the two versions?

Right now, I cannot even save the app, from my PC, in the multi
version
option from the SaveAs dialog - It tries to save it - gets to 16k -
pauses
for ages (20+mins) - then tells me "Document not saved" without a
reason.
The first time it did tell me that I would have to change the
protection on
the VBA code, which I did, as a project which is protected for
viewing
cannot be saved. I have managed to open the app on a PC with Excel
2000 and with changing the calendar control it appears to run fine
except
for the sort function I used - some options were not acceptable.

I would appreciate any comments any one has to offer. Thanks.

Chrissy.