I've been tasked with migrating one of my Access applications to a web front-end.
Right now, it's in Access97 in a back-end/front-end configuration.
My forms are heavy in VBA code for automation and validation.
I don't use reports in Acess. Instead, I just make locked-down continuous forms since they have more functionality (like being able to double-click an order on the report and go to it in the database). I also have buttons on my 'reports' that will dump them to Excel.
If I use the Save to HTML function, is it going to covert my code over to asp the pages it creates?
How difficult a task is this going to be and what issues do I need to watch out for? _________
Rott Paws
...It's not a bug. It's an undocumented feature!!!
Right now, it's in Access97 in a back-end/front-end configuration.
My forms are heavy in VBA code for automation and validation.
I don't use reports in Acess. Instead, I just make locked-down continuous forms since they have more functionality (like being able to double-click an order on the report and go to it in the database). I also have buttons on my 'reports' that will dump them to Excel.
If I use the Save to HTML function, is it going to covert my code over to asp the pages it creates?
How difficult a task is this going to be and what issues do I need to watch out for? _________
Rott Paws
...It's not a bug. It's an undocumented feature!!!