todd.ayers (5/7/2013)
ok...
minimal Access experience / No SQL experience and I am going to assume no app dev skills either...correct?
you talk about existing databases...what platform are these currently on...who currently manages them...could those people assist you?
if your app is mainly read only / reports then I wouldn't get too hung up about "locks"...
if it going to be mainly data entry (create/amend/delete) then you will need a reasonable level of experience in any front end on how you intend the app to manage situations where possible locking may occur...and manage it gracefully so that the user understands what is happening.
Todd...I do not wish to dissuade you from your pursuit...only to point out that there is no easy way and a steep learning curve ahead;..whatever your preferred option.
Good luck.
Unfortunately no app dev skills either. I have an IT background and a degree in computer science but nothing concerning RDBMS. The current databases are on the Access 2007 platform and not being currently administered. I was given this position because I already worked for the company and the plant manager knew I had the closest background available to address issues that are arising.
Concerning the Databases themselves there will be 50/50 relationship between entering data within the databases and retrieving reports and other data from those databases.
Welcome to the wild, wild world of the data professional. Keep your hands and feet inside the vehicle at all times and avoid shrinking databases and using no_lock hints.
But seriously, you're stepping off into some deep weeds here. I'm not saying don't do it. Absolutely. Go for it. Access is actually a good way to learn the basics of both development and database management. But it does have some gotchas. I'd strongly recommend doing some research to track down a book specifically on Access as a front-end development software. They're out there. That will be your best friend going forward. If you get stuck on SQL Server points, always stop by here. If you get stuck on Access stuff, I'm not sure where to send you. Maybe we have an Access forum too. If not here, then try Microsoft Developers Network (MSDN) because I'm sure they do.
Best of luck. Go slow. Learn how to take backups of the SQL Server database before you do anything else.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning