my doubt is simple today, the answer, might not be that simple as I can't figure it out on my own.
How can I have a field on an access form where the user can input an image?
The idea is simple, on the company i work for, there has been a database for my co-worker to fill every time there is a repair on our products to be done.
What he asked me recently is if I can change the database to include a field where he would select a picture he had taken of the damaged goods and add it to the database, so every record on the db would have a picture, ideally hosted on the company's NAS
Thank you for your help
You can use OLE field, and set its type to linked, but this way require NAS with SMB support(windows shared folders or SAMBA) in order to store images at it.
Related
we are currently working on a project of restaurants management, we are using laravel/mysql on the backend and we are looking for the best way to manage invoices pdfs , for now we are just storing theme in a public folder but i think this not a prefect way. we think to send the just the order data to frontend and generate the pdf when the user click on a download button but it's still not efficient, so i need an idea to manage pdf invoices and get theme any time the user wanted them without hurt performance.
Storing the data in a database and then retrieving it as well as generating a pdf upon user request is the most efficient way. Saves your storage space and bandwidth. Any other means would be much more consuming.
I need to link a document uploaded by a member.
Which is by using an upload button to a download button on another page in Wix website builder.
I don't have any issue with programming it, but I would prefer not to if possible.
Depending on exactly what you want, this could be doable without any code, or a minimal amount of code, and also using a database collection.
How you setup your collections will depend on exactly what you want to do, but it sounds like you will at least need one field that references one of the Members collections and another field to hold you file.
On the upload page, add a dataset (either write-only or read-write depending on you setup) for the collection and connect the upload button to that collection. Depending on your setup, you might need to write a line or two of code or use filters on the dataset to upload the file with the correct member info associated with it.
On the download page, you do pretty much the same thing. Add a collection (read-only) and connect the button to it. Again, you might have to filter the collection or write a bit of code to make sure you're getting the file that is associated with the current member.
In an Access 2013 Web App, I created a relationship by changing a field type to "lookup" and set a related table/field. Now I want to remove the relationship. Whenever I try to change the field type to anything besides "lookup", it tells me I must delete the relationship in the Relationships menu, which doesn't exist in a Web App.
The MS support pages just link back and forth without ever answering this glaringly simple issue.
MS Support Instructions for relationships in Access 2013 (not web apps)
How to create a relationship in an Access 2013 Web App (not delete it)
Good question. I agree that the message we display is a little misleading because the instructions only apply for Access desktop applications. I'll see if we can perhaps change that message. I think it is shared across desktop and web app but I'll ask around. I'll see if we can maybe update the help content articles too. I can't make promises of course, but I'll check on that too.
In any case, to delete an established relationship in an Access 2013 web app, you'll have to delete the lookup field itself. If you need to keep the existing data for some reason, you could temporarily create a new column in the table, use a data macro to copy all of the contents from the lookup field you want to delete into the temp column, and then delete the lookup field itself. You could then copy that data from the temporary column into a new column if need be.
I hope that helps.
I would like to create a web page, which documents manually-inputted data about user permissions, that looks like below, which is really pulling data out of a MySQL table.
The way it should act is that whenever someone updates the table to overwrite a value, the old values are stored in a log as a "past revision" -- Which I have no problem on the database side, but I want those past revisions to show up behind the current data on the website, as seen below.
Someone needs to be able to see the current data at a glance, but also the past revisions that expand somehow when clicked. I want this done without having the page refreshed, so maybe jQuery or some active scripting?
That's the heart of the question here, is what technology can easily accomplish the needs of this interface? What do you guys recommend? Examples would be very beneficial. Thanks in advance.
You may try out SVG (along with some jquery for some rich interface):
http://www.w3schools.com/svg/default.asp
I wanna create a table somehow in wondows phone that holds data that never changes and the application querys that data. Pretty simple but not sure how to do it.
Example
a table with Name, Description
When you open the app all the theres an input box to enter a name then you press a button and the description displays.
Using isolated storage seems like you are writing all the data to a file everytime the a user opens the app. Is that how it works?
Using isolated storage seems like you are writing all the data to a file everytime the a user opens the app. Is that how it works?
No, IsolatedStorage is storage - you can think of it as "disk" - so everything in it is persisted between application runs.
When you first run your application, then you'll need to create your files there, but after that time, then the files will already be in place.
If you need to put a large amount of data into IsolatedStorage and then need to search that data later, then "lite" database solutions like http://sterling.codeplex.com/ or SqlLite might help
For test purposes simply hard code the values as a dictionary.
In the long term I suggest you store the information as a file in isolated storage.
Here is an article that describes how to load and save data to isolated storage