Hello All,
I'm currently running through the trial version trying to get a rough "proof-of-concept" web app going in order to get the Credit Card from my boss, but I'm missing some key info. I might err on the side of too much info so please bare with me:
We use Visual Manufacturing from Infor (running on SQLServer) as our primary software solution. I would like to add a few custom tables to our existing SQLServer DB to house our quality system data. I have a couple tables up and running, with A5 looking up data from Visual tables and using that info to populate the new tables with the added quality data (RMA info, for example). The scenario I can't seem to figure out is this; how do I pass the new primary key field data (created when a new issue is submitted, called CIR_ID) from one page to a new detail info page after submitting. I foresee needing to pass that number around from page to page and I can't seem to figure out the mechanism. Should this be a session variable? As far as I know, the resulting auto-incrementing number isn't generated until the new record is inserted, so how do I "get it back" from SQLServer before/while moving to another page?
Another question involves grid-linker components.. For each new CIR_ID there are potentially multiple line items (employees,depts, etc) that are involved with a single issue, so I have another table to capture this data. How do I get that CIR_ID to populate the appropriate field in a linked child grid for all the line-item instances having to do with a single issue? I thought that having the parent-child relationship defined would do this, but it doesn't seem to work that way...
Can field lookup results be enforced so that the only way to update that field is via the lookup? For example, an internal rejection of a workorder must always relate to a unique (Visual) workorder number so I would want the user to have to use a lookup to avoid typos, laziness etc..
One more question about the application server.. Where is this typically installed in a Server2003 enviroment? We have a single SBS2003 server that provides many functions for us (Exchange,SQLServer,file server,among others..). It has its built-in default website for access to OWA and RWW,etc so I am curious about how the application server will cooperate. Our usage of A5 would be intranet only, no outside access. (not now, anyway). Is it better to have WAS on it's own pc? I don't foresee ever needing to service more than 10 concurrent users, with 1-3 being more typical.
Thanks for taking the time to consider my questions..
Erik
P.S. I'm not a programmer and I know nothing about HTML so I'm sure hoping A5 can automate as much as possible until I can start learning what I need to know..!
I'm currently running through the trial version trying to get a rough "proof-of-concept" web app going in order to get the Credit Card from my boss, but I'm missing some key info. I might err on the side of too much info so please bare with me:
We use Visual Manufacturing from Infor (running on SQLServer) as our primary software solution. I would like to add a few custom tables to our existing SQLServer DB to house our quality system data. I have a couple tables up and running, with A5 looking up data from Visual tables and using that info to populate the new tables with the added quality data (RMA info, for example). The scenario I can't seem to figure out is this; how do I pass the new primary key field data (created when a new issue is submitted, called CIR_ID) from one page to a new detail info page after submitting. I foresee needing to pass that number around from page to page and I can't seem to figure out the mechanism. Should this be a session variable? As far as I know, the resulting auto-incrementing number isn't generated until the new record is inserted, so how do I "get it back" from SQLServer before/while moving to another page?
Another question involves grid-linker components.. For each new CIR_ID there are potentially multiple line items (employees,depts, etc) that are involved with a single issue, so I have another table to capture this data. How do I get that CIR_ID to populate the appropriate field in a linked child grid for all the line-item instances having to do with a single issue? I thought that having the parent-child relationship defined would do this, but it doesn't seem to work that way...
Can field lookup results be enforced so that the only way to update that field is via the lookup? For example, an internal rejection of a workorder must always relate to a unique (Visual) workorder number so I would want the user to have to use a lookup to avoid typos, laziness etc..
One more question about the application server.. Where is this typically installed in a Server2003 enviroment? We have a single SBS2003 server that provides many functions for us (Exchange,SQLServer,file server,among others..). It has its built-in default website for access to OWA and RWW,etc so I am curious about how the application server will cooperate. Our usage of A5 would be intranet only, no outside access. (not now, anyway). Is it better to have WAS on it's own pc? I don't foresee ever needing to service more than 10 concurrent users, with 1-3 being more typical.
Thanks for taking the time to consider my questions..
Erik
P.S. I'm not a programmer and I know nothing about HTML so I'm sure hoping A5 can automate as much as possible until I can start learning what I need to know..!
Comment