Jump to content

Runtime Extension USR


This topic is 7290 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Recently I installed Visual Studio.NET. I have now found that the runtime files with the FileMaker standard USR extension have a conflict with SQL User Script files. (At least that is what their icons now show.)

If I try to bind solutions with the USR ext. then I get an error stating that the extesion is used by Windows and won't let me do it.

1. Anyone else find this problem? This is going to cause some issues in upgrades for some clients.

2. Where does one go to find safe extensions?

Thanks

Link to comment
Share on other sites

Hi Roger, i find this to be a good resource on file extensions:

http://whatis.techtarget.com/fileFormatA/0,289933,sid9,00.html

If you have existing USR files that you can't open directly because of this conflict, you could create a shortcut with the target:

"C:Program FilesFileMaker Pro 6FileMaker Pro.exe" C:directoryfile.usr

And if you want some REAL fun, look into changing the registry keys involved. Open regedit and search for USR; anything you find under HKEY_CLASSES_ROOT will pertain to this issue. But DON'T do this unless you're completely comfortable editing the registry, cause you can really mess things up if you're not careful. And please don't blame anything on me; you're on your own, bud! smile.gif

Jerry

Link to comment
Share on other sites

This topic is 7290 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.