ContributionsMost RecentMost LikesSolutionsRe: possible to export entire table to csv?Oh! I don't know how I missed that. Thank you! ------------------------------ Sarah Clark ------------------------------ possible to export entire table to csv?Is there a way to export all the contents of the table? I could build a report that includes all of the fields, but I'm wondering if there's a faster way. ------------------------------ Sarah Clark ------------------------------ Re: file attachments in synced tablesMy hero comes through again! Have a great weekend.file attachments in synced tablesI've created a public-facing app where people can upload attachments. In a private app I've created a Quick Base Sync connection to the relevant table. Is there a way to get the file attachments to come over? Right now it just creates a text field with the name of the attachment.Re: how to create a ""submit"" buttonThe user would still need to do something proactive to indicate "I'm done"- whether it's checking a box manually or clicking a button. The simplest solution would be to have them check the box manually when they are done and then Save and Close one last time. But for various reasons, a button is better for my users.Re: how to create a ""submit"" buttonThank you. I tried this and it didn't work -- it made the button, but it didn't do anything when I clicked it. In any case, I'm looking to do things in the opposite order - save the record first, and then have the button do whatever else it does. As it stands, if you click the button before you've saved, it gives them error messages they don't know what to do with. I've got a text on the form that says "Save any changes before clicking submit," and that may be the best I can do, but in my perfect world I'd have a button for them to "save and submit.Re: how to create a ""submit"" buttonOkay, so I have this button working great. Is there a way to have the button save the record too? As it stands, the user must first click save and close or save and keep working. My users have an antipathy toward save buttons because they are used to a database which doesn't require that. So I'm looking for as many ways as possible to avoid that step. If a form rule will do the trick too, that would be fine, but I haven't been able to figure one out. Re: how to create a ""submit"" buttonThat would indeed be simpler. However, these are all new users (we're just rolling out Quick Base) and it's easier for them to understand a big colorful button that they can access in either view or edit. Simple for them trumps simple for me.Re: how to create a ""submit"" buttonThank you thank you!Re: how to create a ""submit"" buttonUpdate: I gave it a try, and the formula above partly works, in that clicking the button checked the checkbox. However, it brings me to a page that says the following: This XML file does not appear to have any style information associated with it. The document tree is shown below. <qdbapi> <action>API_EditRecord</action> <errcode>0</errcode> <errtext>No error</errtext> <rid>266</rid> <num_fields_changed>1</num_fields_changed> <update_id>1562778829707</update_id> </qdbapi>