Jump to content

CaseyBailey

Newbies
  • Posts

    3
  • Joined

  • Last visited

CaseyBailey's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. This is a fairly easy problem that most languages/systems handle gracefully, but I'm relatively new to FM in general and can't figure out a more streamlined process than the extremely-time-intensive method we're using now. The situation: We're constantly developing a rather large FM solution in-house. We have 30+ clients who purchase our solution. We then host a separate instance of our solution for each client on a server we control running FMS12. Everything works fine BUT -- Let's say we release an updated version every 2 weeks that includes scripting/layout bug fixes and new functionality. Right now, our way of upgrading all clients to this new version is to manually Close each client's instance by hand, download it from FMS to the desktop, manually replace the old db file with our new one while leaving the external container folders intact, rename the old db file to "Source", then manually run a large script that imports all of the client's database data from "Source" into our new version. We then have to re-upload this 'upgraded' version to FMS and restart it. This *DOES* work, in that it keeps client images/data intact while replacing the FM scripting/layouts with our new versions, but I'm sure you can tell just how outrageously long this takes to do by hand. As we gain more clients, the time required is becoming entirely unmanageable and I feel like there HAS to be a better way that I simply don't know about. Help please
  2. Thanks for the quick help! Sadly, I'm just the lowly programmer and my boss refuses to continue using SuperContainer for various reasons. I'm checking out the white paper now though!
  3. This problem is absolutely driving us nuts, and has been for a week straight. Full disclosure, I just started this job and have never worked with FM before, so I have no doubt we're just missing something. Here's what's happening: We have an application that stores all of its images in an external container field set to [hosted location]/[database location]/Files/Container. The images were originally stored inside of SuperContainer, so we wrote a quick script to import them into the new version of our application. This worked fine. The issue we're now having is that we have a variety of servers as well as clients running our app on their own local servers, and deploying a new version of our .fmp file erases the link to every single image. This is a problem we absolutely have to fix, since we really can't rely on re-importing 20+ gigs of images into every new release for 20+ clients. Help please!
×
×
  • Create New...

Important Information

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