Demo disks?

[Lloyd Frank]

I would like to get some comments on demo disks, their value, problems, percent of purchases or any other problems or experiences other users have had offering demo disks.
I am thinking about doing this and I am not sure if it is a good way to go.

Thanks for any comments

Lloyd

[Bill Warner]

RE: Demo disks?

I designed an app for the Lupus Foundation in Michigan a year ago. Last month, the man from Lupus took a demo of my program to the national conference, and six other chapters requested a demo. I sent them, and so far 3 chapters have bought the program.

This is a fabulous success rate, but I suspect it's not typical. But to answer your specific question, I think any time a potential customer can actually try the software, they are much more likely to buy it.

I set up my trial disk with the complete program, but put scripting in so they were limited as to how many records they could enter. I like this approach better than limiting some of the functions (such as making forms read-only), because they can actually USE it, rather than just looking at the pretty screens.

[Lloyd Frank]

RE: Demo disks?

Bill

Thank for the info.
I was thinking of giving them the entire program, but limiting the use to 30 days. Do you think that limiting the records is a better approach?

Lloyd

[csda1]

RE: Demo disks?

Lloyd,

I can't tell you how many times I've seen people get a 30 day demo and not be able to use it even in 90 days to try it out. Better it should be for 30 uses, or a certain amount of time, etc. That way, when the user is ready to try it, he can.

Just my thoughts,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Lloyd Frank]

RE: Demo disks?

I have it set so that it will be 30 days from the time it is run the first time. I hope this will give the user time to try it even if they wait 6 months to use it the first time.

[Jim Rowlen]

RE: Demo disks?

I've never had a problem installing a demo so that it would run for as long as I wanted. With my schedule I hae to (it might take me a couple months to be able to look at it). There is a way to block that but very few are set to take advantage of it.

A demo with a limited number of uses is better since a customer might have a full schedule. If the customer looks at yours first, then a few others, and gets back to yours in 45 days for a final evaluation he can't work with anything other than his memory. Usually at this point he wants to check/compare a few specific features. If it's a situation where someone is giving a demostration of different packages to his boss a couple months later he won't be able to show your package unless he reinstalls it (unless you've also taken steps to prevent that method of getting around the time limit).

[Lloyd Frank]

RE: Demo disks?

Jim

I hadn't thought of that happening, when I get a demo I try it as soon as I get it. Maybe the number of uses or number of records will be a better way to go. Don't have time to change it now. Someone wants a copy asap, but I will try some of the changes.

Thanks to all for your ideas amd suggestions.

Lloyd

[shaun]

RE: Demo disks?

Hi,

I was intrigued by your answer. I thought a record limit
was an excellent idea. Is there any info anywher on how to write this kind of script and where to place it?

Thanks.

[Steve Buckler]

RE: Demo disks?

Shuan,

On the CanSaveRecord event in the field rules you will have to retreive the number of records that are in the table with .records_get(). If you are restricting your demo to only allow the user 50 records then you will need the following xbasic:

dim tbl as p
tbl=table.current()
if tbl.records_get() >= 50 then
cancel()
end if

I hope this helps.

steve

[Ron McCormack]

RE: Demo disks?

I use a record limit on the forms new button, but it could be on the can enter event for the table.

I check the record count and if it is greater than the limit required cancel the operation

A sort of code to use would be

dim rcnt as N
dim tbl as P
tbl=table.get()
rcnt=tbl.records_get()
if rcnt

[shaun]

RE: Demo disks?

Thank you both Steve & Ron.

Wow! What a list this is! I'm really happy to have come across both Alpha Software and this list!

[csda1]

RE: Demo disks?

To All,

Record limits are nice for some application demos, but are not a particularly good idea when an application has the potential to get large (e.g. 20,000 or more records). To limit a user means he will not be able to test it in a manner that it would be used.

My top 10 other ways of crippling an application are;

10. No user customization (if you have any)
9. No Import of data (limited to sample data and user input)
8. No export
7. No printing (or maybe only a certain # of printouts maximum - People do want to see what it looks like)
6. Limited uses of whole application or just particular functions
5. Limited # of days of usage (keep track of the day has changed and if so, decrement counter)
4. Enabling only say, 2 features at a time for a use (ala CoolEdit96 shareware)
3. Allow no changing of Data (only enter)
2. No Network usage (there are ways of locking the application to 1 user)

and finally the number 1 way to cripple your application is.......

1. Constantly make changes, add features and especially, fix bugs!!!!

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]