Results 1 to 4 of 4
  1. #1
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Questions (Access 97)

    I created a database that was supposed to be a temporary solution but now will be used as a tracking system for our department. I am a little concerned because I have had some bad experiences with the database - it becomes corrupted so easily. I have copied forms from backups and sometimes have to repair etc.. I have to be constantly backing up or doing some type of maintenance. I am not an expert Access developer. I know how to create forms, reports and use some Visual Basic and macros but I am by no means an expert. My questions: How many records can Access 97 store? Is there a way once a field is filled in that it can't be changed? I hate to get into security but can some users have editing rights and deleting rights and others not and if so is it difficult to do?

    Right now the records are manually input but they want to have a feed from an Oracle database that updates certain fields automatically according to a trigger. I am just not sure that my little Access database is the way to go. Anyone have any suggestions?

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

    Re: Questions (Access 97)

    In this group you are bound to get lots of suggestions - here's my <img src=/S/2cents.gif border=0 alt=2cents width=15 height=15>:
    <UL><LI>If you are having corruption problems, I would suggest you first look at splitting your database into a front-end and back-end arrangement. Then I would move the front-end to the individual user's PCs. That can get to be a pain if there are lots of users (say > 10), but then you would be able to simply replace the front-end if a user's forms became corrupt.
    <LI>I would also check to see if you are using memo fields - they are more prone to corruption problems - and if possible replace them.
    <LI>I would also look at upgrading to either Access 2000 or 2002 - either is more stable than Access97, which will soon be no longer "officially" supported by Microsoft.
    <LI>If you continue to have corruption problems with the back-end after you have split it, I would look at storing your data in the Oracle database using the ODBC driver that is available for Oracle.[/list]As to the capabilities of Access, you can store a million records or more quite easily in Access - the only limit is the database size. Check the help file for Access97 and search for specifications - from memory I believe it will tell you the maximum size is 1GB. As to locking records, you would need to do that with Access security as long as you use an Access back-end, and that would also allow some users to edit and others to just view. Security can be complex, but once you get the concepts down it's simpler than writing VBA - I would suggest you look at the white papers available from the MS web site, or refer to one of the many Access books that delve into it.
    Wendell

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Questions (Access 97)

    In addition to Wendell's excellent suggestions, I would encourage you to make it clear to your superiors that you are NOT a professional Access developer, no matter what they might think. Then ask for help, either a consultant who IS an experienced developer or additional training before they expect you to be able to produce a robust application. Do-it-yourself isn't a bad thing, but if they're in a hurry then you need instant expertise. It's simplest and usually cheapest to simply hire that expertise to work with you. You will learn a lot from it, and the company will get the database they need sooner.
    Charlotte

  4. #4
    2 Star Lounger
    Join Date
    Feb 2002
    Location
    Blacktown, Sydney, New South Wales, Australia
    Posts
    175
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: Questions (Access 97)

    Linda,
    I totally agree with the two previous posts. Sometimes the likes of you and I are limited by our boss's imagination. The problem with temporary solutions, is that we tend to go too light on the planning stage. After all its only temporary. Any future 'enhancements' tend to be 'band-aid' solutions. The big advantage of an experienced developer, that he/she should PLAN your database, and may see a much more efficient way to collect/report your data.

    A final note. Always regard yourself as being armed with enough knowledge to make you dangerous. Then before jumping in, seek advice.

Posting Permissions

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