|
I hear ya, but when a client wants to pay me to work on it, I take it.
There's a "Delphi" forum. I think an MS Office forum would be nice. I'll post in Bugs & Sugs
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I think you missed the point. The answer was Stack Overflow (website). It wasn't a dig on the job.
|
|
|
|
|
Whatever the Access question, the answer is always "Hey Mr. Client, we love Access but it's time to grow up and move to a big-boy database..."
|
|
|
|
|
There are plans in the works to move to an enterprise architecture.
And an no point do you ever say no to a client who's willing to pay.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: And an no point do you ever say no to a client who's willing to pay. Indeed! I was trying to be funnyish but I did like Access as a tool back at version 1 and 2. Worked really well.
|
|
|
|
|
Kevin Marois wrote: And an no point do you ever say no to a client who's willing to pay. Sure you do. Some clients will drain you dry if you don't learn to say no.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I told a couple of clients "no", but wound up having to do what they asked anyway.
One of them I put off for six months before implementing their customer-hostile feature.
The other wanted me to make a change to their production system while I was at their site -- I tried to insist on not doing it until I got back to the office and folllowing the proper procedure, but they insisted.
|
|
|
|
|
Then you don't charge enough.
|
|
|
|
|
That is another way to say no.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Yes, like 'Which part of no did you not understand?'
|
|
|
|
|
Same goes for women.
Jeremy Falcon
|
|
|
|
|
As I always say, it's not the tool that is used that causes the problems, it's the tool that uses it.
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
|
I'm waiting for the naysayers to ask why on earth you would consider using Access for anything. Just the other day I came across a system still using Access 97 databases for the backend. This is a fairly popular (in my niche) inventory system...It may be popular, but it really sucks as it can only ever provide values at a point in time, not for a point in time like all the others I've dealt with. Of course my manager forces me to spend days trying to match a report that was printed a week prior.
Sorry to have hijacked your question...I think Database is the right forum. Of course you could always just submit in QA.
"Go forth into the source" - Neal Morse
|
|
|
|
|
This is a typical Access app. It was created by someone who needed a small tracking system and over time it morphed into a mid to large size app.
They have plans to create an enterprise level app, first to SQL Server, then into .Net/Web/Mobile.
kmoorevs wrote: .I think Database is the right forum.
I considered it, but this isn't really a data question. It's more about the VBA than anything else.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I've had considerable experience with Access and VBA but I sure wouldn't admit it in polite conversation.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
The answer is always to do the steps manually while recording a macro.
|
|
|
|
|
Surely you have a daily backup that you keep for a month before you replace it with the monthly backup! I learnt this was the best solution for reproduction of Access stuff in the 90s.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Surely you have a daily backup
Good idea, but not my call. It would probably work, but I refuse to put any more time into interfacing with a system using Access 97 databases ...I mean, c'mon, at least move them to 2K!..or better yet, rewrite the application to use SQL Server!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Yup when dealing with stubborn idiots who won't listen it is sometimes correct to let them shoot themselves in the foot. I told you so can be very satisfying sometimes.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Just stick it in QA and tag it appropriately;
"SQL, ADO.NET, Entity Framework, c#, c#3, c#4, c#5, MVC, MVC3, MVC4, MVC5, Oracle, VB.Net, VB"
Well, that's what everyone else does anyway.
|
|
|
|
|
|
[^]
Jeremy Falcon
|
|
|
|
|
The code supported by Access would be VBA. So the VB forum would be the right place.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Tip: use SQLite, it is more portable and Open Source, so you arent locked in the Microsoft universe.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|