Results 1 to 4 of 4
  1. #1
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Leuven, Vlaanderen, Belgium
    Posts
    322
    Thanks
    9
    Thanked 0 Times in 0 Posts

    Back/forward converting fe&be while developing OK? (97/2K)

    Dear members of the board,
    at my office we use Office 97. I have developed a database with a front and back end. The development for the next version might be done on my portable which uses Office XP. Therefore, I suppose it's best to convert both front- and backend to 2K, do my thing (structural backend + front end changes) and convert back to 97 for use at my office. This might be repeated several times.
    I do I risk any data damage or other corruption? Then I'll have to change plans...
    Hasse
    p.s. The backend contains already data of a previous working year (which I'll try to convert and keep available in the database. It appeared better to me to do the changes on the good-data-database then to make all changes and then import all data from the original one. Is that a good choice too, or does that really make no difference...

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

    Re: Back/forward converting fe&be while developing OK? (97/2K)

    If you take care not to use Access 2000/2002 specific features, it should be possible to develop in Access 2002. Make sure to make backup copies frequently.

    Importing existing data into new tables can pose a problem with AutoNumber fields, you'd have to take care not to destroy relationships.

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Back/forward converting fe&be while developing OK? (97/2K)

    Actually, if you are going to stick with 97, I don't see any compelling reason to convert the back-end, as all you are doing is connecting to its tables. The only downsides we've seen in that arrangement is a fairly significant performance hit, and a tendency to corrupt more frequently - but in a development environment neither of those are likely to hamper you.
    Wendell

  4. #4
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Leuven, Vlaanderen, Belgium
    Posts
    322
    Thanks
    9
    Thanked 0 Times in 0 Posts

    Re: Back/forward converting fe&be while developing OK? (97/2K)

    Both, thanks for your feedback <img src=/S/bow.gif border=0 alt=bow width=15 height=15>!

    Hans, thanks for pointing me at the Autonumber issue! This makes me even more sure not to try to (if I don't need to) 'develop elsewhere and then import'
    And yes... of course... thanks for remembering... <img src=/S/razz.gif border=0 alt=razz width=25 height=17> backup backup backup

    Wendell, thank you too... just FYI:
    <hr>Actually, if you are going to stick with 97, I don't see any compelling reason to convert the back-end, as all you are doing is connecting to its tables. <hr>
    I have to covert the backend to allow me to make the database structures: new fields, new tables & relationships (tblA<->tblB becomes tblA<->tblC<->tblB), etc.
    <hr> The only downsides we've seen in that arrangement is a fairly significant performance hit, and a tendency to corrupt more frequently - but in a development environment neither of those are likely to hamper you.<hr>
    Yeah... I've read around here about those 97 backend - 2K frontend -issues too. And I think I got a hit already too <img src=/S/grin.gif border=0 alt=grin width=15 height=15>. As I started with some front-end changes first, Access went down a first time already, far too soon. I wouldn't be surprised if the not-yet-converted backend had something to do with it <img src=/S/hmmn.gif border=0 alt=hmmn width=15 height=15>.

Posting Permissions

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