Best Practice

  • I am new to the db admin field and would like some guidance on an issue I am faced with. I have been asked to build several different access front end applications tied to custom built tables in our sql server db. On each instance I could have easily setup an excel spreadsheet to store the data and give the appropriate rights to the individual assigned with updating the spreadsheet. What is the right thing to do? I worry about the future when I am gone and we have all these access applications on our network. Who will maintain them? We have already ran into runtime issues on a couple of access applications we have implemented. Any help or guidance would be greatly appreciated.

  • Excel, do you mean just editing data in tables? Like lookup data? Access will work, but tends to lock the entire table.

    you might be able to build some simple ASP.NET pages to handle this.

    Is this just to maintain limited data for a few people?

  • Yes. Limited data for just a couple of people.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply