I wasn't sure if this was a good place for this topic but thought I would try it out.
I have recently been informed that a huge data collection project that is being launched (originally planned to use SQL Server, VB6.0, ASP) is now being moved to a solution under Adobe eForms.
From what I understand this software just allows you to do data entry on a "form" that is identical to a PDF design, then when saved it saves it as a PDF as well. I also read that the data entered can actually be stored or read from a database.
Just for some background, I am very familiar with database design, Access, VB6.0 and Classic ASP (as well as HTML\CSS). However, I have never worked with these "eForms" before and apparently they are wanting me to get into it.
Also the system in question is going to have a massive amount of validation checks, record sequence checks, and the database design in a fairly complex one with 30-40 look up tables for drop downs, and alot of one to many type of relationships.
My question is basically this:
Will I have trouble adapting to the Adobe eforms software? Does anyone know what kind of custom coding will be allowed with something like this? if any? Are eforms really a good solution for this system?
It seems like the learning curve that will appear for using this Adobe software with PDFs is going to be just as cumbersome as designing a interface\syste m from scratch using web programming.
Anyone have inside knowledge?
I have recently been informed that a huge data collection project that is being launched (originally planned to use SQL Server, VB6.0, ASP) is now being moved to a solution under Adobe eForms.
From what I understand this software just allows you to do data entry on a "form" that is identical to a PDF design, then when saved it saves it as a PDF as well. I also read that the data entered can actually be stored or read from a database.
Just for some background, I am very familiar with database design, Access, VB6.0 and Classic ASP (as well as HTML\CSS). However, I have never worked with these "eForms" before and apparently they are wanting me to get into it.
Also the system in question is going to have a massive amount of validation checks, record sequence checks, and the database design in a fairly complex one with 30-40 look up tables for drop downs, and alot of one to many type of relationships.
My question is basically this:
Will I have trouble adapting to the Adobe eforms software? Does anyone know what kind of custom coding will be allowed with something like this? if any? Are eforms really a good solution for this system?
It seems like the learning curve that will appear for using this Adobe software with PDFs is going to be just as cumbersome as designing a interface\syste m from scratch using web programming.
Anyone have inside knowledge?