Who would have thought, building a database could be so complex!

 

Mind you, it has been over 20years since I did anything with MS Access

I've done a couple for work recently.

 

I'm the only one in our team that has any clue with Access.

 

It's only been about 10 years since I used it though

 

What kind of thing you been doing?

 

Phil

I had a brainwave last night.  I thought, how difficult could it be to build my own database that will

 

* Store customer details (name/address/phone/email etc)

* Store bicycle details (serial number/make/model etc)

* Allow me to create PDI/Servicing & Repair forms that link into the serial number of the bicycle

* Stock list

 

& the ability to search on previous repairs/print completed PDI/Servicing/Repair forms for the customer.

 

..Note.. this is an on-going idea and the more I think about it, the more I think I could make it do. :'(

 

I know there are probably templates etc I could download, but, where's the fun in that. It's a slow day at work & it would be good to understand it so I can continue to develop it over time

Friendly warning - Unless you're registered, I think your proposed database may be a breach of the Data Protection Acts.

Probably not that hard but relational databases are as much art as science. If you've not touched it for years it'll be a steep relearning curve.

 

I used to know lots about Access but like you I've not really touched it for more than 10yr and I doubt I could do anything very easily now.

 

Last time I tried to do it I found I could remember how to write SQL queries but not use the GUI on Access.

Friendly warning - Unless you're registered, I think your proposed database may be a breach of the Data Protection Acts.

 

true.

 

But it's not hard to register and you'll need to add a privacy policy to your documents and take reasonable care of the information (£35 a year to register).

 

https://ico.org.uk/for-organisations/register/

Take the self assessment. Every time I've done it, it's come out as not necessary. I think the big switch question is, if you share the data.

 

Great you mention bicycles the data modelling book I'm reading at the moment is all about bikes. It's 400 odd pages too. So bikes can get incredibly complex yet the purpose is simplifying it all

 

For something I'm working now, displaying a list of 'features' I feel like I'm reinventing half the world to say if a ski chalet has a dvd player. Sometimes you get to close and stuck in...

 

Will get to your PM soon too, just need to make a red cross or green tick appear next to this dvd player.

oh and, if you password protect it, it's no use, you can still read the data off a linux machine Had the joy of demonstrating that to an IT expert who didn't want the data online... I also mentioned I'd downloaded the database from his cloud storage Yeah one of the better days.

 

It's good for prototyping though! My SWMBO is good on access and data modelling. Puts me to shame, but I can't convince her to come over to the world of IT.

Friendly warning - Unless you're registered, I think your proposed database may be a breach of the Data Protection Acts.

 

 

true.

 

But it's not hard to register and you'll need to add a privacy policy to your documents and take reasonable care of the information (£35 a year to register).

 

https://ico.org.uk/for-organisations/register/

 

I've taken a look at the link provided, whilst I intend to make a profit, no information is to be shared with anyone, it is purely for keeping track of work carried out on products & to give me the ability to track down customers to the best of my ability should a manufacturer issue a recall.

 

 

Will get to your PM soon too, just need to make a red cross or green tick appear next to this dvd player.

 

No rush, I'm heading home soon and don't intend to return to a computer screen until I have to.. I've really enjoyed not having to look at a screen to work.

oh and, if you password protect it, it's no use, you can still read the data off a linux machine Had the joy of demonstrating that to an IT expert who didn't want the data online... I also mentioned I'd downloaded the database from his cloud storage Yeah one of the better days.

 

It's good for prototyping though! My SWMBO is good on access and data modelling. Puts me to shame, but I can't convince her to come over to the world of IT.

There are other ways around Access "security fig leaves" too, like "not being a member of the workgroup the db is part of on the network": that means that Access treats you as a "database administrator" and gives you full access.

I've taken a look at the link provided, whilst I intend to make a profit, no information is to be shared with anyone, it is purely for keeping track of work carried out on products & to give me the ability to track down customers to the best of my ability should a manufacturer issue a recall.

"For profit" isn't the test. It's whether or not you are processing "personal data" within the meaning of the Act. I'd say that "Namadd" + "Owns Muddy Fox MTB" is personal data.

I'd check if the version of Access you are using supports encryption (this is different to password protection as Colin has implied).

2010 - https://support.office.com/en-in/article/Encrypt-a-database-by-using-a-database-password-12aa0e5c-34c6-4957-af3b-b5f5cfa9a766

 

The crypto in Office 2003 isn't very good but 2007 onwards use decent AES algorithms which are as good as anything around. Just use a decent strong password.

 

If you're not sharing and you are protecting the data you store then I can't see you having a problem.

 

I had a run through the questionnaire too and wondered if it would apply if you were to use the database of customers for 'marketing' i.e. Dear Sir your bike is due an annual service.

 

For £35 you might want to register anyway.

Edited 14 May, 201511 yr by Aspman

Ahhh Access the MS program that wasn't even developed by MS, with terrible security etc.

 

Personally for basic use I'd be looking at SQL Express, easier and more secure.

 

http://www.microsoft.com/en-gb/server-cloud/products/sql-server-editions/sql-server-express.aspx

Personally for basic use I'd be looking at SQL Express, easier and more secure.

 

http://www.microsoft.com/en-gb/server-cloud/products/sql-server-editions/sql-server-express.aspx

 

You would still need something to generate the front end in, and therefore you would have to expose your data to Access to build the forms.

 

Otherwise if the OP knows how to configure and SQL Server and write a .net application to connect to SQL server then by all means, but I suspect that isn't the case.  Plus you can still crack SQL server security, I watched a video on that the other week.

My Database is on our secure work system so security isn't a concern for me.

 

I have used it to create a database to manage debt we have secured against properties.

 

We use it during the initial set-up to generate forms and letters to send to the customer and also to help monitor the return of these forms.

 

It's still a work in progress and will be used to produce half-yearly debt and interest reports to send out (daily compounding interest has caused me some real headaches!).

 

Phil

My Database is on our secure work system so security isn't a concern for me.

 

 

Unless your network is totally disconnected from the internet/outside world, you shouldn't consider it secure, and even then are there systems in place to prevent CD/DVD burning, USB sticks/HDDs, and only allow authenticated machines network access.  Someone with physical access could still steal your DB.

 

Security should be every developers concern.

If someone hacks into our network then they would have access to a lot of confidential data. It is behind our network security/firewall etc. It's as safe as any other data on our network.

 

I work for a local authority by the way.

 

Phil

Ahhh Access the MS program that wasn't even developed by MS, with terrible security etc.

 

Personally for basic use I'd be looking at SQL Express, easier and more secure.

 

http://www.microsoft.com/en-gb/server-cloud/products/sql-server-editions/sql-server-express.aspx

Name an "MS product" that was originally developed by MS. I can't.

If someone hacks into our network then they would have access to a lot of confidential data. It is behind our network security/firewall etc. It's as safe as any other data on our network.

 

I work for a local authority by the way.

 

Phil

At that rate you should have someone who's job title is "Data Protection Officer", probably as part of whatever your Information Services department is called. Talk to them, now, or well Monday morning might be better.

I had a brainwave last night.  I thought, how difficult could it be to build my own database that will

 

* Store customer details (name/address/phone/email etc)

* Store bicycle details (serial number/make/model etc)

* Allow me to create PDI/Servicing & Repair forms that link into the serial number of the bicycle

* Stock list

 

& the ability to search on previous repairs/print completed PDI/Servicing/Repair forms for the customer.

 

..Note.. this is an on-going idea and the more I think about it, the more I think I could make it do. :'(

 

I know there are probably templates etc I could download, but, where's the fun in that. It's a slow day at work & it would be good to understand it so I can continue to develop it over time

You may need Word as well to hold the forms/repair templates.I did this once for a Year 2000 project - a system with about 3000 (yup, 3000!) software modules that had to be checked. Word docs for forms to print off for the developers to use/fil-in, MSAccess d/b to hold the data and the module details, and to enter the investigation resuts/change update/test update etc. Then reporting tools to monitor overall status. Took 3-4 days intensive work to prepare (including a learning curve).

 

Skills to develop - MSAccess data storage/reporting/data entry screesn, MSWord templates inc. form fields, MailMerge