alternatives to access as a front-end

[pandapark]

I've written an access database - which over time has grown into quite a complicated system especially its validation, multi-page screens, tabs, links to external systems, arrays, etc. I'm moving the tables to SQL as I write and have a web front-end for searching/viewing data.
my new boss seems to be somewhat anti-access and is intent on re-writing as a web front-end, which i have said would take a long time and wouldn't be able to achieve the same level of functionality as maybe access could (i'm thinking the validation at real-time especially)
assuming I manage to persuade her to not use the web as the answer for inputting data what alternatives to access as a front-end are there? alot of the external system we will link to will be written in SQL.
And how can i improve my argument against re-writing the inputting side to be done via the web! I'm sure someone will say whatever you can do in access you can do using asp/javascript whatever.

regards
ian

 

[BNPMike]

Almost every programming environment under the sun will connect to a Jet database (via eg ODBC). So you choose.

The easiest I would guess is Visual Basic ie .NET.

The arguments for dumping Access are

1) saving licence costs
2) no need for Access skills.

Argument against:

1) large investment for zero gain in terms of business functionality.