Shortcut doesn't work

This is a wild guess from something that happened to me

It sounds like someone might have changed or updated the database from a floppy, so that when it opens it is looking for a floppy.

Try having a blank floppy in the drive and opening it. If this works, try opening something and save the database. Close the program and restart it without the blank floppy in it.

If there is an .ini file associated with the exe that opens it, you might find a line in it referencing the floppy. Youmight be able to (after making a copy of it) change the reference to the directory where the program is located.

Search the registry for entries for the clipper database and look for the same type of entry mention above

good luck

Right click it , select properties, select go to sourse, make another short cut to the execute, hold down the Shift Key and drag it onto the desktop and delete the old one. But only if the execute is good, try it first, and shut it back off if it operates, then make the new shortcut, and dump the old one.
Luck

Select properties on all dlls and Executables, check the path and correct it to show the file location on the drive. It's the same as the Short-cut properties sortof, as they all should show the C:\Drive file (Or which ever drive it's on)it looks like one is trying to call a drive up that is not necessary, in this case non-existant, like when you place a shortcut on the desktop that leads to a CD you don't have in at the time.
Hope it can easily be found, but find all pieces of it, as it has to be one one of them , as it operates the other way.

Addendum:

It should be said that the database program is DOS based. Also, the shortcut(desktop) will work randomly.

The flaky desktop-based shortcut version (and application) is pointing to which mapped drive letter on your peer to peer network? (e.g., possible you have multiple "C:" drives booted at a given time?).

You may have already checked this, but doesyour app reside on a unique-to-it drive mapping or 'share'?

Havent been this way for a while and I'm sorry you haven't solved the problem. I have run into this sort of difficulty before, as it is the registry where the path is stored, like a malfunctioning Demo, only way to solve it is copy all the install onto the drive , and install it from there, but likely the first disk will have to remain on the drive, sorry , but it seems the maker was worried about pirates, and took too many steps to prevent it. Hope this works as ,if the maker was really paranoid, it won't. Like i said, it is routed in the registry.

Well, the old pc got the boot. New machine in place and new DB slated to replace the antique. Everyone, Thank you for your efforts.

This question was closed by the author