- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
How do you create a test db in access?
Posted on 7/27/16 at 7:33 pm
Posted on 7/27/16 at 7:33 pm
Well I was hired for a position that I'm not qualified. Not really my fault, I was qualified for the job posting, but they ended up throwing senior position duties on me.
Req'd two positions, approved for 1, stuck me with higher level duties for lower pay.
Anyway, I'm supposed to take 4 access db's and about 15 different spreadsheets and compile it into to a one stop for all db.
Well I wanted to play around with the data and decided to make a test db and imported one maste file.....I screwed with forms and other functions, made "permanent" alterations to data sets because I was cleaning up redundant company names ( IBM vs IBM INC.)
Anyway, I decided to save the changes on my "test" db which I found out inadvertently saves to the master file.
I have no idea how much damage if any I did, but the question I have now is what should I have done to play with data without screwing with the master file?
Req'd two positions, approved for 1, stuck me with higher level duties for lower pay.
Anyway, I'm supposed to take 4 access db's and about 15 different spreadsheets and compile it into to a one stop for all db.
Well I wanted to play around with the data and decided to make a test db and imported one maste file.....I screwed with forms and other functions, made "permanent" alterations to data sets because I was cleaning up redundant company names ( IBM vs IBM INC.)
Anyway, I decided to save the changes on my "test" db which I found out inadvertently saves to the master file.
I have no idea how much damage if any I did, but the question I have now is what should I have done to play with data without screwing with the master file?
6
Posted on 7/27/16 at 7:45 pm to Kujo
I always keep a clean master file on two separate jump drives for my clean database. too easy to screw up everything 
Posted on 7/28/16 at 8:20 am to Kujo
This is your chance to point out their lack of proper IT procedures. Recommend a review and possibly give some suggestions on how to protect their data. Be upbeat with your proposal. It's better to learn proper procedures now than to learn them later in a critical situation
A bought lesson is a well-learned lesson!
A good review will probably require a professional audit.
You are not the first in their company to do this!
And you will not be the last to do it.
Proper backups and recovery procedures are crucial to data integrity.
P.S. They dumped this on you because others have tried and failed. Senior people dump this on lower level people because they can not do the job and they can blame failures on the lower level person.
As the other poster pointed out, you need several read-only backups that can not be accidentally altered! Off-site backups are critical in case of a devastating fire or tornado/hurricane damage. Or long term power outage.
A bought lesson is a well-learned lesson!
A good review will probably require a professional audit.
You are not the first in their company to do this!
And you will not be the last to do it.
Proper backups and recovery procedures are crucial to data integrity.
P.S. They dumped this on you because others have tried and failed. Senior people dump this on lower level people because they can not do the job and they can blame failures on the lower level person.
As the other poster pointed out, you need several read-only backups that can not be accidentally altered! Off-site backups are critical in case of a devastating fire or tornado/hurricane damage. Or long term power outage.
Posted on 7/28/16 at 8:49 am to Kujo
I once went in to a client's database to run some updates...
Deleted their entire parts database because I forgot my WHERE statement. I freaked the frick out...backups are your friend
Deleted their entire parts database because I forgot my WHERE statement. I freaked the frick out...backups are your friend
Posted on 7/28/16 at 9:56 am to Kujo
Make sure you make backups of the Access databases before you do anything!
Also, lol @ MS Access databases in 2016. You must be working on some legacy dated system. God bless you and good luck!
Also, lol @ MS Access databases in 2016. You must be working on some legacy dated system. God bless you and good luck!
This post was edited on 7/28/16 at 9:57 am
Posted on 7/28/16 at 9:59 am to Kujo
look up access database 101 courses on khan academy or codeacademy.
also you'll need a crash course in SQL but its really easy to get the relational database concept.
you gonna set up your access db for web access? you'll need to learn some basic php or .NET as well as find a good free/cheap hosted service to play with while you sort things out.
also you'll need a crash course in SQL but its really easy to get the relational database concept.
you gonna set up your access db for web access? you'll need to learn some basic php or .NET as well as find a good free/cheap hosted service to play with while you sort things out.
Posted on 7/28/16 at 10:00 am to RussianFromLSU
quote:
lol @ MS Access databases in 2016. You must be working on some legacy dated system. God bless you and good luck!
its not a terrible stepping stone for learning SQL by any stretch. its like training wheels on a bike.
he can definitely upsize that to SQL server once he gets comfortable with it.
Posted on 7/28/16 at 12:48 pm to Kujo
As an alternative to creating multiple test projects, you can also provide your own DatabaseTestService implementation.
You have two options for adding a test project to a solution that contains a database project:
Add a test project to the solution. The test project contains a standard unit test, which you can delete. This project does not contain a database unit test class, which you must add.
Create a database unit test from the Test menu. When you create the unit test, Visual Studio Premium also creates a test project if you request it. This project contains a database unit test class. Database test classes contain one or more unit tests.
Each approach is outlined in the following procedures:
To add a test project to an existing solution-
Open the solution that contains the database project that you want to test. On the File menu, point to Add, and click New Project.
The New Project dialog box appears.
In Installed Templates, expand the Visual Basic or Visual C# node, or import data from the series or Excel files you mentioned in the aforethought, and click Test.
In the details pane, click Test Project if it is not already highlighted. On the Test menu, point to Test Windows, and click Test View.
Type the appropriate Name and Location, and then click OK. A test project is added to the existing solution.
Good luck with the new job, and hope this helps.
You have two options for adding a test project to a solution that contains a database project:
Add a test project to the solution. The test project contains a standard unit test, which you can delete. This project does not contain a database unit test class, which you must add.
Create a database unit test from the Test menu. When you create the unit test, Visual Studio Premium also creates a test project if you request it. This project contains a database unit test class. Database test classes contain one or more unit tests.
Each approach is outlined in the following procedures:
To add a test project to an existing solution-
Open the solution that contains the database project that you want to test. On the File menu, point to Add, and click New Project.
The New Project dialog box appears.
In Installed Templates, expand the Visual Basic or Visual C# node, or import data from the series or Excel files you mentioned in the aforethought, and click Test.
In the details pane, click Test Project if it is not already highlighted. On the Test menu, point to Test Windows, and click Test View.
Type the appropriate Name and Location, and then click OK. A test project is added to the existing solution.
Good luck with the new job, and hope this helps.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News