Search results

That is a really great idea and incredibly simple. Thank you very much. Here I was trying to rewrite the DoCmd.OutputTo source code when I could basically just use a dummy report/form for all the printing and exporting. It will also simplify managing how it looks in form view vs print view.

It still creates the same problem. Every instance of the form will have the same name and so it will only print/save the first instance of the form in the forms collection, which will most likely be the first instance opened. So, if I'm trying to print the last instance I just opened it will...

Is there an equivalent to DoCmd.OutputTo or DoCmd.PrintOut where i pass the form object instead of passing the form name? I have a form where multiple instances may be opened and so I cannot use the form name as a reference. But the only methods I'm aware of to print a form or save as a pdf...

So, I did attempt to change my tables around some. Instead of having multiple date fields in the master table I made a table to house all the dates with a field for datetype to identify what action within the process the date corresponds with. However now I'm completely lost on how to even use a...

I understand normalization but this data will be dates that need to be tied to individual accounts and may not always be the same for a given set of accounts.

Interesting example but I'm unsure how I could leverage it to solve my issue. Perhaps there was a miscommunication on my part. By update multiple records at once I mean the user enters data into three textboxes, hits update, and it updates three different fields for every record within a...

I currently have an unbound form (parent form) for data entry. And a datasheet subform based on a query that pulls accounts the user needs to work. My reasoning behind using an unbound form is because the user needs the option to update multiple records at once and I'm unaware of how to do...