3 ms·
Actually, I think your reasoning is flawed here. 1. They should just use something like replicon ( http://www.replicon.com/ http://www.replicon.com/ ) for that
by eckyptang 14y ago
Actually, I think your reasoning is flawed here.
1. They should just use something like replicon ( http://www.replicon.com/ http://www.replicon.com/ ) for that. Don't build if something already exists.
2. Lightswitch solutions are not designed to be sold by consultancies of external developers. They are designed to be in house built and maintained as per VBA apps.
Access is still doing fine for a number of cases. I still have to maintain an Access 7.0 database for inventory tracking/management on NT4 which I built in 1997. It still does the job so there is no reason to replace it. I will be early next year moving it to Access 2010 on Windows 7 as their hardware is now dying miserably and that is the only motivation to upgrade it. Note: this is running on SQL6.5 with 50 users.
- tluyben2 14y agoWhy is my reasoning flawed? Which part exactly? The part where people internally write horrible software on these 'code less' platforms? Company critical software which then somehow needs to be maintained by some poor programmer? I just tell what I see in real life and that's not pretty. Maybe your Access db wasn't such a mess. If you have over 50.000 lines of VBA written by people who never programmed but learned it organically by changing the application, then i'm not sure if it shouldn't be replaced. Any change to that system is a huge danger.