I've only recently started on Access - because my clients all liked and understood Access and think its the best thing since sliced bread. The fact they can make their own ad-hoc queries is a bonus to them.
If I mention the development effort and cost to go vb or .net with a SQL Server/Oracle backend their eyes rollup and they pass out.
Doesn't matter whether we think its a proper DBMS or not, clients want it done in Access and I ain't gonna argue with them.
- 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!
Reply to: Access SQL help
Collapse
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 "Access SQL help"
Collapse
-
i've spent most my career upgrading Access apps to SQL/VB systems...
just thought i'd mention that
Leave a comment:
-
Originally posted by xoggothSticking with the purely practical. For smallish apps, as has been said, it would be perfectly adequate if it was not SO FECKIN' FLAKY! Do other databases (or "databases") get into unrecoverable totally buggered-up modes quite so easily? I imagine not.
Leave a comment:
-
Originally posted by TheRightStuffIt is a database and a pretty good one at that. good for small apps.
You some SQL server / oracle monkey?
Leave a comment:
-
Aaaaah!!! The old Access is/isn't a real database thing. This is not so much a technical discussion as a religious one.
Sticking with the purely practical. For smallish apps, as has been said, it would be perfectly adequate if it was not SO FECKIN' FLAKY! Do other databases (or "databases") get into unrecoverable totally buggered-up modes quite so easily? I imagine not.
PS The way it edits SQL really pissed me off too. If you had a query that used result of another query and then changed output name of that, it never just let you get round to editing that as necessary, it had to stick in loads of [Never 'eard of it] AS etc. PISS off ACCESS!, who is programming this you or me? I think some applications just need a damn good slapping.Last edited by xoggoth; 9 July 2007, 18:25.
Leave a comment:
-
Originally posted by TheRightStuffIt is a database
Leave a comment:
-
Cheers lilelvis2000, I ended up using 2 separate queries/views, one that references the other one, in the end as you suggested.
Leave a comment:
-
Originally posted by andrew_neil_ukyes - using Access. try using a database
You some SQL server / oracle monkey?
Leave a comment:
-
Nothing wrong on your part. that's just what Access does. It is a pain when you need to edit it again. The "best" way to do this is not use a subquery but create a query and use it within another one. You can dynamically change this query to your liking without messing things up.
I do the same with my forms which use a passthrough query which is dynamically re-written when combo boxes on the form are changed.
Leave a comment:
-
Haha yes very good, I would if the client had anything else.
Solved it thought... had some more [ ] square brackets in the subquery/derived table when naming fields that were screwing things up.
Leave a comment:
-
Originally posted by MrRobinAm I doing something wrong?
Leave a comment:
-
Access SQL help
Hi,
I'm having a fit with the way Access is rewriting my SQL once I have saved a query and then reopen it...
I am quering a subtable a bit like this:
Code:Select mytable.name, mytable.cost From ( Select name, cost, date, store From sometable Where cost > 100 ) mytable
Code:Select mytable.name, mytable.cost From [ Select name, cost, date, store From somestable Where cost > 100 ]. as mytable
Am I doing something wrong? What do I do to turn off automatic query editing in Access?
Thanks very much.
RobinTags: None
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: