Form vs. Spreadsheet

[Brian C]

I have created a spreadsheet (Excel 2000) that allows for user input (with
drop downs and option buttons).

My concern is that a user could save this sheet to their desktop, rather
than downloading the sheet from a centralized Lotus Notes database. If the
user does this, they won't have the most current version of the sheet.

Would a userform provide the capability to stop a user from saving the sheet
and missing out on updates? NOTE in the spreadsheet, I have already disabled
the Save and Save As functions with VBA code, but if they don't enable the
Macros they can still save it to their C drive.

I also played with the idea of saving it as an Add-In, but the spreadsheet
didn't transfer over correctly.

I would appreciate any help in resolving these challenges.

Thanks,

Brian

 

[JE McGimpsey]

I have created a spreadsheet (Excel 2000) that allows for user input (with
drop downs and option buttons).

My concern is that a user could save this sheet to their desktop, rather
than downloading the sheet from a centralized Lotus Notes database. If the
user does this, they won't have the most current version of the sheet.

Would a userform provide the capability to stop a user from saving the sheet
and missing out on updates? NOTE in the spreadsheet, I have already disabled
the Save and Save As functions with VBA code, but if they don't enable the
Macros they can still save it to their C drive.

I also played with the idea of saving it as an Add-In, but the spreadsheet
didn't transfer over correctly.

First, note that this is a Macintosh Excel group - you may choose to use
the Windows Excel groups in the future such as

microsoft.public.excel.misc

if you have Windows Excel specific questions.

It's difficult, if not impossible, to keep a user from saving locally,
especially if macros are disabled. I can't see how a userform would be
helpful here since it won't display without macros being enabled.

With macros enabled, you could check the

Thisworkbook.Path

property against your preferred directory - *IF* the file has been saved
(the property is blank if the file hasn't been saved).

Another way might be to save the revision as a document property and
check that document property against the latest revision number stored
on the network, perhaps in a text file. That would require that macros
be enabled.

There are undoubtedly dozens of other methods, but I'd think they'd all
require macros to be enabled.