PDA

View Full Version : Free MS Access Shop Management - Here You Go!


steve1040
04-22-2011, 01:47 PM
Here is my contribution to this site:

I've been holding off on sharing this for about 6 months because I don't want someone selling it. My desire is that this will be a free tool for people just starting out. Most people have MS Office and should be able to run a small shop with it. Once you've had a chance to use a management program without limitations then you know what functionality to look for when buying a true management system.



I've been developing this MSAccess Shop Management Tool since last year while laid off from my full-time job. I've since found a new job and have not had a chance to do anything else with it. It's functional and you can build on it. Please don't sale it.

It's designed to work in a shop
If has a 2 databases
Backend DB is on a shared network drive and hold all the ticket and customer info
Client DB can be placed on any number of machines within the shop.

Tickets are checked out by techs and checked in when finish.
Manager can assign tickets to techs.
etc

I have written a good Setup document to get anyone up and going with this

Maybe a donation if this helps you but it is not required.

Cadishead Computers
04-22-2011, 02:28 PM
Hi Steve, I have to say this program has some really good features. It is well written, however I have a couple of queries..

The countries, are very limited, ie china, japan, us, canada etc. How about techs from other countries, is it possible they can add their chosen country?

Also within the address part, you have state listed, that would only be applicable to those in the US. In the uk we have counties.

For techs who are just starting out in business, I think they would find it of great use. For those of us who are experienced, I think it is a little too basic for our requirements.

But overall, I think it is a well written database, and kudos to you. The instruction manual is also well written and simple enough to follow.

14049752
04-22-2011, 02:45 PM
It looks like a good start as far as the logistics...as far as the function...I don't understand it.

The UI needs some work here and there. Windows open and aren't sized correctly, and I'm having trouble figuring out some of the way it works at first glance. For example, I can't figure out how to add notes to a ticket when logged in. I can change the customer and equipment type, and all of that, but I can't figure out how to enter notes regarding what the status is of the ticket.

What are the "add title" and "delete title" buttons supposed to do when viewing tickets? When I click them, I just get a runtime error. (I didn't look in design view, too lazy :D )

When I click the "invoice" button on a ticket, the report shows as blank.


Basically, I'm sure this works since you know how to use it...but it looks foreign to me....as I'm sure my program would look to you.

Peaceful
04-22-2011, 02:54 PM
Any way to get this working in access 2010? Instructions aren't jiving, when I click on database tools there's no database utilities selection.:confused:

14049752
04-22-2011, 02:55 PM
In Access 2010, just click database tools, then click the linked table manager button.

Peaceful
04-22-2011, 03:03 PM
I must be using a different access 2010, found my linked table manager under external data, not database tools.;)

steve1040
04-22-2011, 03:05 PM
Hi Steve, I have to say this program has some really good features. It is well written, however I have a couple of queries..

The countries, are very limited, ie china, japan, us, canada etc. How about techs from other countries, is it possible they can add their chosen country?

Also within the address part, you have state listed, that would only be applicable to those in the US. In the uk we have counties.

For techs who are just starting out in business, I think they would find it of great use. For those of us who are experienced, I think it is a little too basic for our requirements.

But overall, I think it is a well written database, and kudos to you. The instruction manual is also well written and simple enough to follow.

I agree if you're experience then this won't be useful - As most experienced users have already purchased or developed a tool.

But for those starting out this has the basics and they can modify to suit there situation including adding other countries

K007
04-22-2011, 04:54 PM
Thanks for sharing.
Had a look at the underlying database (back-end) and did see some fundamental mistakes.
You are using Foreign Keys for look-up fields.
As Access is a relational database, there will be problems in manipulating the data, creating reports, etc.
For example table CustomerCases has 4 foreign keys. That means it is the slave (detail) table of 4 other tables which are it's master.
That is a flawed concept, and although it may function as a database, it will not be of much use.
For example in table Customers why did you need to make ZipCode and Country fields as foreign keys? For look-up purpose you don't need that, it can be safely achieved with in-line SQL to fill up your drop-down menu and simply make the field required.

Edit:
Did analysis of the model and came up with only 1 big warning (this is a design problem, not functionality like the many foreign keys):
Object: Reference2
Page: MainPage
Warning: Foreign key datatypes don't match (ZipCodes.ZipCode - Customers.ZipCode)
Whatever you do, fix this. Make it string type, because other countries have letters in their zip code. And integer types are only needed if you do calculations, other than that, even if there was to be only numbers, if there are no calculations on the values, the field should be string type.

Peaceful
04-22-2011, 04:58 PM
No clue what any of that ^^^^ means but whatever, it sure looks like it'll do what I need it to and can't beat the price :)

K007
04-22-2011, 05:13 PM
No clue what any of that ^^^^ means but whatever, it sure looks like it'll do what I need it to and can't beat the price :)

That ^^^^ means lots of headaches, trust me.
Make sure you got a good friend in the chemist shop. :)
Oh, and it wasn't intended directly to users, but to it's maker.

steve1040
04-22-2011, 05:15 PM
Thanks for sharing.
Had a look at the underlying database (back-end) and did see some fundamental mistakes.
You are using Foreign Keys for look-up fields.
As Access is a relational database, there will be problems in manipulating the data, creating reports, etc.
For example table CustomerCases has 4 foreign keys. That means it is the slave (detail) table of 4 other tables which are it's master.
That is a flawed concept, and although it may function as a database, it will not be of much use.
For example in table Customers why did you need to make ZipCode and Country fields as foreign keys? For look-up purpose you don't need that, it can be safely achieved with in-line SQL to fill up your drop-down menu and simply make the field required.

Edit:
Did analysis of the model and came up with only 1 big warning (this is a design problem, not functionality like the many foreign keys):
Object: Reference2
Page: MainPage
Warning: Foreign key datatypes don't match (ZipCodes.ZipCode - Customers.ZipCode)
Whatever you do, fix this. Make it string type, because other countries have letters in their zip code. And integer types are only needed if you do calculations, other than that, even if there was to be only numbers, if there are no calculations on the values, the field should be string type.

Fill free to make those changes and improve this offering

K007
04-22-2011, 05:20 PM
Fill free to make those changes and improve this offering

I'm too busy as I am, and use something else for my tickets.
On the other hand, to me there is no such thing as free lunch. I don't work for free :)

Edit:
Anyway, improving the design of the database would have no effect, the guy who wrote the whole thing would have to change
quite a lot of code as well. Not a job for me.

mkeathley
04-27-2011, 02:20 AM
Thank you for this!
You rock :-)

baccart
04-27-2011, 04:13 PM
Is there a link to download this? I am sorry, I am not seeing it.

TimJacobs
04-27-2011, 04:20 PM
It looks like the OP removed it

K007
04-27-2011, 08:38 PM
It looks like the OP removed it

Maybe he is fixing the problems I mentioned above.

CainComputerSpecialists
06-12-2011, 10:01 PM
I would like to use this program if it is still available.

steve1040
06-13-2011, 08:34 PM
I would like to use this program if it is still available.


I'll send it to you later tonight - The only thing that has change is that I hired a guy from Vworker to add a method for collecting payment through Paypal. I haven't had a chance to test the new payment feature.
I've recently bought "Another Repair Tracker" and I won't be investing anymore time or development into the Access database.

UPDATE: See original post

steve1040
06-14-2011, 01:35 PM
See original post for database - No need to send PM

CainComputerSpecialists
06-17-2011, 04:28 AM
Thank you I will give this a try.

Bushcat
06-17-2011, 07:09 AM
Brilliant! Works well and has definitely got a massive potential. You can see the thought and effort put into it.

I think this will be very handy for folks starting out on tight budgets.

Thanks Steve!

CainComputerSpecialists
06-18-2011, 10:02 PM
I have just started to use this program and looks fantastic!

Thank you

steve1040
06-19-2011, 12:38 AM
I have just started to use this program and looks fantastic!

Thank you

Cool - It's always good to know someone is benefiting from my work.

fixitdaz
06-19-2011, 08:34 PM
@steve1040 we are having a play with the db but we are having problems with the check in button, i cannot see the check in button any help would be much appreciated.

2.2.3 When work is complete on the ticket, and you are read to check it back into the queue for the next process, click the “Check In” button

fixitdaz
06-20-2011, 09:04 AM
I Have added an image i think i maybe missing something.
Screen shot (https://picasaweb.google.com/103958988538126742367/Jun202011?authkey=Gv1sRgCJvQ1bjvn8eL4gE#5620224444 162487410)

Ok We have figured it out, we needed to login as user not admin so Pleas disregard my last two posts.
On anther note not a bad db if you are starting up Thanks for the share.