Results 1 to 3 of 3
  1. #1
    Lounger
    Join Date
    Jun 2002
    Location
    Michigan City, Indiana, USA
    Posts
    37
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Updating versions of commercial software (2003)

    My office uses a commercial database which uses Access. Over the last 4 years, we have made many tweaks and changes to the design of this database to better suit our needs. I keep this list of changes on an Excel spreadsheet. The bad part is, each time this company comes up with a new version of this software, I have to go in and make 3 years worth of changes again. This takes a lot of time. My boss is very much for using this company's software and not developing our own because of their technical support. Is there any way to save the changes I've made as sort of an "image" that I could just paste into the new version without somehow affecting the changes the company has made to improve the new version.

    Hope this makes sense.

    Jodi

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Updating versions of commercial software (2003)

    It very much depends on the nature of the tweaks and of the changes applied by the company, but in general it won't be easy.
    Your best bet might be to write VBA code that applies the tweaks instead of applying them manually. That way you can run the code again when needed. But if the company changes the design of a database object drastically, the code might not work any more.

  3. #3
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Updating versions of commercial software (2003)

    I'm assuming you've made changes to forms, queries, and reports, not just developed some new additional ones?

    In which case the answer is: No there isn't.

    You might try telling the developer what all your changes are. He may incorporate at least some of them into the release version, this would eliminate you having to redo everything each time. There is also an outside chance (probably slim) that he might maintain a separate version of the database for you, perhaps for an increased maintenance fee. This would be offset by the time you spend redoing all your changes each time.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •