Hello Bartho,
Thanks for your reaction. Virtual fields? I just did a search in the pdf-manual of Scriptcase for “virtual fields”. Nothing to be found. Non existing in the Scriptcase-world.
What do you mean? Could you post a working upload-app with document and image upload-fields both for filename- as database-administration?
/Scriptfan
Not called Virtual Field, called “Virtual Input” …
What he means is that! Virtual input you create an input in SC without the same in this database.
The upload option works but the SC. Test with an application CONTROL. Create an application control then create an input named “Upload” then check the “Document (file name)” or “Picture (Database).”
Take this quiz and tell me!
Bartho, you use some translation (google translation)? if yes, the translation not help you very well … because the translation (google translation) does not reflect the feeling of the words … the classic example is the topic where the staff do not know what is “Field”, which actually would be an “input”.
Bartho, se voc? usar 100% o google para traduzir, n?o ser? de muita ajuda, isso pode ate confundir mais o pessoal! Campo para eles ? como um Lugar (place) ou uma ?rea, “Campo de futebol” por exemplo (Football Field), embora para n?s ? um input (campo). Apenas uma dica, estou aqui para ajudar de cora??o!
Scriptfan,
Sorry for not being clear enough. I meant that instead of using a field that is mapped to your database, you should use a created field (http://s11.postimg.org/o08rlhvcz/Sem_t_tulo.png).
Fred,
I don’t use google translate. Are you sure about field and inputs? As I see input is usually used as “entrada” and field as “campo”.
De qualquer maneira agrade?o muito o toque heheh!
regards,
Bernhard Bernsmann
[QUOTE=FredKeyster;18223]Not called Virtual Field, called “Virtual Input” …
What he means is that! Virtual input you create an input in SC without the same in this database.
The upload option works but the SC. Test with an application CONTROL. Create an application control then create an input named “Upload” then check the “Document (file name)” or “Picture (Database).”
Take this quiz and tell me![/QUOTE]
thanks for your reaction.
if i start with a control app i can only define inputs/fields with filename administration. and that works. but i want to upload documents/images with database-administration. so to do that i started with a form-app based on a database-table created for storing the upload-metadata. and on that form-app next to the fields of the database-upload-table i created an upload input/field and that does not work, but gives the error-message as stated in my opening-post.
see my post in reaction to fredkeyster.
it doesn’t work.
another week has passed without a solution by scriptcase. it’s not working by itself again. the upload-project is on hold because of this. people here wonder why this is happening with a paid tool. i uploaded a couple of screenshots to show the problem:
what is causing the error-message about being only one upload field allowed in the second screenshot? the scriptcase-manual is not of any help. someone inside the scriptcase-organization programmed that error-message. who? could someone ask him/her when this message is shown to the user?
/scriptfan
I’m not sure I fully understand the issue, but I believe you are looking at having multiple upload fields within the same app. My apologies if I am not fully understanding.
I recently finished an app that required 4 upload fields in the same form. For each field, I created a new table specific to that upload field. I then created a new field for the upload using the “Add Field” button in the “Fields” menu. In the Settings page for each field, I assigned the unique table to the field. This allowed me to reference the same record ID for the foreign key for the upload table. I believe each upload field needs to identify a foreign key.
So, what I learned from that exercise is that form doesn’t use an upload field in the table from which you are creating the form app, but rather it uses an add-on field to store the document data. I have not tried to get those files to show on a grid yet, but I imagine it would be a similar process.
Hope this is helpful.
hello travler,
thanks for your reaction. i understand all what you write and that’s how it’s supposed to work, but it doesn’t in my setup.
i’m not looking for having multiple upload-fields in one app. at least not yet. i only have ONE upload-files in the form-app, that i want to be administered with one table. the system allows me define the field, but saving the multiupload-fields gives the weird error about only upload-field allowed. THERE IS ONLY ONE UPLOAD-FIELD as can be seen in the screenshots.
if i click something else in the object-tree on the left the system is willing to compile the app and run it without further error-messages, but WITHOUT the administering the upload-metadata in the database-table. and that’s logical, because it didn’t want to save the multiupload-field definitions.
it’s completely ridiculous that this problem cannot be addressed by scriptcase. my collegue (rr) has posted another upload-problem, which also is not solved by scriptcase. bartho only keeps passing the info to developers. and after that nothing happens.
scriptcase should be called BUGCASE.
and another week has passed without a solution or reaction from scriptcase.
bump bump bump
Barto,
All these bugs in the uploader are related to each other. This is a serious issue on several occurances within the university currently. Give it high priority now please!
