On 11/24/2023 5:47 PM, Stéphane CARPENTIER wrote:
> Le 21-11-2023, DFS <
nos...@dfs.com> a écrit :
>> On 11/18/2023 5:25 AM, Farley Flud wrote:
>>> On 17 Nov 2023 22:43:55 GMT, Stéphane CARPENTIER wrote:
>>>
>>>>
>>>> For a sophisticated database app, there are real programming languages
>>>> and real databases. Access is just good to try something fast. When you
>>>> want real people to use it, with time it becomes a nightmare.
>>>>
>>>
>>> So, very, very TRUE.
>>
>>
>> So very, very BOGUS. Stephane is just being an MS-hating
>
> Until there you are right.
Picking on MS Access is a sure sign of a Microsoft-hater. And it's
usually also someone not talented enough to use the powerful
capabilities of Access. Like Feeb Russell.
>> drama queen -
>
> But there you become confused. Does Joel provide you some drugs?
>
>> that comes free with Linux.
>
> As there are more Windows users than Linux users, the drama queens are
> mostly using Windows.
no no no no no
Most Linux users bitch endlessly about MS and Windows, but the reverse
is not true.
>> "with time it becomes a nightmare" is just meaningless babble.
>
> No. It's experience.
>
>> The passage of time isn't going to change the Access application.
>
> Of course, if you don't use your application, it doesn't change. And
> nothing is wrong with it. Except if you try to use it once your system
> does an upgrade and your Access version is no more compatible with the
> version it was written. But if you are using it, you add more and more
> functionalities and you have more and more users and it becomes very
> difficult to understand.
>
>> If he means "we want changes to the application and database and nobody
>> around here can do it and it's become a nightmare" then he's describing
>> every technology that ever existed.
>
> Yes, but with Access, it can become way more difficult. First because it
> wasn't often a developer who created the application, but someone who
> knows better than the others and who do it for the all team. Then there
> are a lot of way do do things with access and when you try to change
> something it can be tricky to understand where the action is triggered.
Yes. All that is true. And all that is true for any sufficiently
sophisticated technology.
All the problems you describe can be minimized or eliminated by having
trustworthy, professional, experienced Access developers design, create
and document the systems. If the customer asks for a lot of
functionality, an Access application can become very big and VERY
difficult for newbies to understand. Hundreds of objects (tables,
queries, forms, reports and macros) and thousands of lines of code you
didn't write are hard to dissect. So the company has to bite the bullet
and pay for experienced talent to do maintenance and upgrades and documents.
The same would be true of any C++/Qt application, etc.
>> If he means "we upgraded Access versions and now the old app throws
>> errors and the developer doesn't work here any more and it's become a
>> nightmare" then he might have to hire a new developer to update the
>> application.
>
> That's not always that easy. Once I saw an application developed by an
> intern for a team, because it was cheap, unlike a developer. And at the
> beginning, some people were modifying things without understanding. So,
> he locked everything in his application. And he left with the password.
> And when the team wanted to improve the application, they asked the
> IS/IT team for a dev. But without password, that wasn't that easy.
Access passwords are/were easy to break, but if the intern left you only
a compiled code file (.mde) you could be in real trouble. He should
actually be sued to provide the source code and passwords.