locked
Runtime Application RRS feed

  • Question

  • We have a Filemaker Runtime application.  These runtimes are full self sustainable database applications with their own exe files, dlls, etc...  A user does NOT need to buy Filemaker to use our application.

    In XP, we always installed everything to the C:|program Files\AppName\  folder.  And this worked fine.  This is a single user database application, but multiple users with different login credentials may be logging in and using the application.  So, it's important that all users always see the same database file (there is only one).  It is also important for updates that the update process updates this data file.

    In Vista & Win7, the rules have changed as to what Vista & Win7 allow.  We have a new application that users will soon be installing.  We are in the process of creating our installer and are absolutely lost as to what folders we should be using, etc.....  Some have said put your data file in C:\ProgramData\AppName\.  Others have said it should go in the C:\Users\Public\AppName\ and others have said use C:\Users\All Users\, etc....

    We have run into issues with windows virtual store and file re-direction.  We find the new data being written appears to go to the correct file, but our updates are not updating the correct file.

    Any help you can offer would be greatly appreciated.   It is important that with this new application, we get this one right from the start and follow Microsoft's guidelines.     We expect that 70% of these new customers will still be running XP, and the balance Win7, but we know that this will change to a 90% Win7 within the next year or two.

    TIA

    Tuesday, May 22, 2012 8:11 PM

All replies

  • APP-V is an Application Virtualization tool. I would suggest you try the Windows 7 Forum. C:\Users\All Users is not valid. ProgramData is redirection in Win7 for anything which may have wanted to write to C:\Documents and Settings\All Users\Application Data

    I would try out that as the first shout because it sounds like you are using an old application which is XP certified and not necessarily a Windows 7 version?

    Alternatively, upgrade the version..


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Wednesday, May 23, 2012 6:10 PM