Split Forms: Just. Say. NO!

Just so anyone else is aware, 2007 errors with 'Cannot find file 'Flter'" on
Code: 
cmd.Picture = "Filter"

1585924872208.png

I seem to recall later versions have these built in.?
Easily fixed if needed though.

Thank you MajP
 
I seem to recall later versions have these built in.?
Easily fixed if needed though
Click to expand...
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.

imagegallery.jpg
 
I do not think 2007 has an image gallery?, at least I cannot find it, but would use an actual file path instead.?
 
theDBguy said:
Hi. Would you mind posting a demo of your split form with the broken BeforeUpdate event, so I can learn from it? Thanks.
Click to expand...
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.

In the meantime, here is Gina's code that I adapted.
 
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.
 
zeroaccess said:
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.
Click to expand...
Hi. I'm interested in understanding your comments a little better. Could you please elaborate on your points below?
  1. What do you mean by you can't refer to a record # in the datasheet?
  2. What do you mean by the datasheet will force the entire window's dimensions to the max?
Thanks!
 
it's a small niggle but the only thing I don't like about the shortcut menu is (Select All) scrolls (same in Excel). The number of times I start scrolling, find the value I want then realise I've not unticked the select all option - at least excel has a search box so you can limit the list.
 
theDBguy said:
Hi. I'm interested in understanding your comments a little better. Could you please elaborate on your points below?
  1. What do you mean by you can't refer to a record # in the datasheet?
  2. What do you mean by the datasheet will force the entire window's dimensions to the max?
Thanks!
Click to expand...
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.
 
zeroaccess said:
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.
Click to expand...
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.
 
theDBguy said:
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.
Click to expand...
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/
 
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!
 
NauticalGent said:
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!
Click to expand...
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!
 
Last edited:
theDBguy said:
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!
Click to expand...
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.
 
NauticalGent said:
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.
Click to expand...
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 really. I'll post it tomorrow...its 0130 here and I need to get some sleep!
 
Ok here it is. I have figured out what is causing the issue and I'm sure you will see it much quicker than I did!

At any rate, the issue goes away once you do one of three things:
1. Change to form from split to single.
2. Unhide the ReferredBy field in the datasheet.
3. Remove the code in the OnCurrent event.
 

Attachments

You must log in or register to reply here.

Similar threads

Q
Solved Message no record found
Replies
18
Views
350
quest
Q
J
Solved Not a coding problem
Replies
6
Views
355
gemma-the-husky
gemma-the-husky
J
Can't fill in a subform
Replies
13
Views
413
Jen-Jen
J
W
Very odd VBA error when using Split()
Replies
15
Views
539
WillockBoy
W
J
Splitting my Database
Replies
12
Views
333
Pat Hartman
P

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom