That is the only trick. You save the picture to the image gallery by making it a shared image. Also you make the image type "Shared". This is a little bit of a PIA, and the only hard part of doing this. This allows you to simply call the image by name.I seem to recall later versions have these built in.?
Easily fixed if needed though
I will work on posting a scaled down version when I get back to the office. Getting around on the weekends can be a little tricky because the Carabinieri are out there in force.Hi. Would you mind posting a demo of your split form with the broken BeforeUpdate event, so I can learn from it? Thanks.
Hi. I'm interested in understanding your comments a little better. Could you please elaborate on your points below?Well this noob is using split forms with success, though I will admit there are things I can't seem to do, such as referring to a specific record # in the datasheet. There are probably other things I haven't run into.
I don't like how a split form datasheet will force your entire form window's dimensions to the max and there is no way to control it. If that is a problem you need to change to continuous form view or put your data in a subform instead.
1. I tried variations of Gina's code to return the record selector to the previously selected record after a requery of the datasheet with no success.Hi. I'm interested in understanding your comments a little better. Could you please elaborate on your points below?
Thanks!
- What do you mean by you can't refer to a record # in the datasheet?
- What do you mean by the datasheet will force the entire window's dimensions to the max?
Hi. Thanks for the clarification. You are not talking about the same code from Gina that @NauticalGent mentioned, correct? If so, can you please post a link to it, so I can take a look? I am not sure what you mean by binding the datasheet portion of a Split Form to a query. Did you mean you based the whole form to a query? I mean, the single view form and the datasheet portion of a Split Form both use the same Record Source property. They are not separate.1. I tried variations of Gina's code to return the record selector to the previously selected record after a requery of the datasheet with no success.
2. If you bind a split form datasheet to a query, the resulting window will be huge and it does not respond to setting the window height/width in VBA.
Yes, that is what I mean. Sorry for the confusion.Hi. Thanks for the clarification. You are not talking about the same code from Gina that @NauticalGent mentioned, correct? If so, can you please post a link to it, so I can take a look? I am not sure what you mean by binding the datasheet portion of a Split Form to a query. Did you mean you based the whole form to a query? I mean, the single view form and the datasheet portion of a Split Form both use the same Record Source property. They are not separate.
Hi. Thanks for the update. Do you know if it's possible to modify the code to skip the hidden columns (or at least handle them more gracefully somehow)? Cheers!Well DBG, while I was duplicating the issue, I discovered what the problem is. In the datasheet portion of the split form, you can hide fields. If you try to setfocus on the mainform to a field that is hidden on the data sheet, you run into a problem.
Mystery solved and it just reaffirms my belief that splitforms are just not worth it.
Not a bad days work!
I told you there and I tell you again. Your problem should be something else. Because that code works for me.Yes, that is what I mean. Sorry for the confusion.
The issue I had with the requery was here: https://www.access-programmers.co.u...y-underlying-form-but-retain-bookmark.309650/
Not for certain. If a hidden field is one you want to validate and the. Set focus on then the only work around I could think of would be to unhide the fields in question, finish up the before update code and then hide them again with an after update routine?Hi. Thanks for the update. Do you know if it's possible to modify the code to skip the hidden columns (or at least handle them more gracefully somehow)? Cheers!
Okay, sounds good. However, I have to let you know, I just tried Gina's code on a Split Form with a required hidden column, and I didn't have any problems with it. Her code worked fine for me. Cheers!Not for certain. If a hidden field is one you want to validate and the. Set focus on then the only work around I could think of would be to unhide the fields in question, finish up the before update code and then hide them again with an after update routine?
Even if that were possible, which I'm certain it is, that is a lot of work for something that can be achieved with less work.
I think this just means you're doing some complicated things with your project. I just did a quick simple test. Cheers!Well hell....