Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Can't-believe-we-got-away-with-this thread"
I frequently see crappy access databases like that, more often than not because the client is having a problem with it (again) and wants me to have a look when I've got a bit of spare time.
Usually my response is "Which idiot wrote this crap?"
Which idiot wrote this crap - it is double my usual rate
In their defence, and no I never wrote any app-bases, they did what they needed to do, brought mail merge and report generation to the masses and at a fraction of the cost of the big boy solutions. Also infinitely more flexible.
Wouldn't do it these days but can't help thinking if MS designed a Web version of Access based on a limited implementation of SQL Server and ASP.NET + IIS, they'd make yet more squillions. Probably not worth the investment for them in reality.
Anyone want to go into business with me to make it?
Yes but I believe that Access nowadays is a different beast to back then (does it use a form of SQL Server?).
In the past with JET you were essential using a single file with some attempt at locking and claiming it was an enterprise level database! This file also contained all the code.
No, its still a stand alone product that can use odbc to link to most things, inluding itself. Locking has always been possible, but do it yourself rather than rely on the engine.
It was never a good idea to mix code with tables, anyone who was any good never did that!
Yes but I believe that Access nowadays is a different beast to back then (does it use a form of SQL Server?).
In the past with JET you were essential using a single file with some attempt at locking and claiming it was an enterprise level database! This file also contained all the code.
That's nothing, lad! There were plenty of tulip databases around in t'old days - we worked on one called Revelation based on Pick. In PC form it had zillions of files which contained a mixture of data and programs spread throughout - nice. We had some pretty big users too.
Yes but I believe that Access nowadays is a different beast to back then (does it use a form of SQL Server?).
In the past with JET you were essential using a single file with some attempt at locking and claiming it was an enterprise level database! This file also contained all the code.
And just like plumbers. Tradesmen everywhere they just love telling you how stupid you were to use the idiot "what did that". These people really irritate me. Why cant they dispense with the humiliation bit identify the problem and then sort it out.
I had an honest plumber once who admitted that he couldn't just slag off the original plumber, "cos it was me dad what did it".
Leave a comment: