Are there various options for label locations for a continuous form?

[JMongi]

Right now I have column labels for my continuous form in the form header and they work as you would expect.

Is there a different header/form section they can be placed in and function similarly? I've tried experimenting with pages without success. Of course, its quite possible I didn't know what I was doing! I'd like to have options, if possible. Nothing else really.

 

[theDBguy]

Since you're just asking for options, another one might be to use a subform for your continuous rows and place the labels on the main form. Just a thought...

 

[June7]

Not really. Page section is for printing a form, which really shouldn't do anyway.

Why do you ask? What would you like to have?

Build a report if need to display data in groups.

 

[JMongi]

Since you're just asking for options, another one might be to use a subform for your continuous rows and place the labels on the main form. Just a thought...

@theDBguy - Any benefits to that arrangement? I guess that would unify any other forms. In other words, it's either a "regular" form, a "regular" form that's been made continuous by inserting a subform, or a true split form with parent/child relationships (with a subform obviously).

Edit:
It's minor, but that could fix a minor UI scroll bar issue. My fixed size main form wouldn't have scroll bars messing with them as the scroll bars would be part of the continuous subform. Interesting.

 

[theDBguy]

@theDBguy - Any benefits to that arrangement? I guess that would unify any other forms. In other words, it's either a "regular" form, a "regular" form that's been made continuous by inserting a subform, or a true split form with parent/child relationships (with a subform obviously).

Edit:
It's minor, but that could fix a minor UI scroll bar issue. My fixed size main form wouldn't have scroll bars messing with them as the scroll bars would be part of the continuous subform. Interesting.

Not really sure if there's any benefit. It depends on your taste or needs. Since you said you were just curious about other ways it could be done, it was just something I imagined could be one way of doing it.

 

[JMongi]

Why do you ask? What would you like to have?

@June7 - Nothing too particular. I'm doing some cleanup/standardizing on a project and am starting to think about a default form that has a header with all my design (plus code). The particular form I'm editing had a different header style plus the column labels in it. I was just musing about the header itself remaining constant/consistent with all other forms and having the continuous form column labels in a different section.

 

[JMongi]

Here is what I'm working on just as a quick visual reference. The top form is what I'm editing (in process) and the bottom form is my pseudo-template.

 

[June7]

I suppose the header could include a subform.

I inherited a db that had fancy headers loaded with embedded logo images on almost every form. I deleted and significantly reduced file size. Obviously didn't resample the images to reduce size. I really don't see benefit of slamming users with this 'billboard' style info on a daily basis. I think they know the company they work for.

Now a report for printout is another matter.

 

[JMongi]

I agree generally. However, this company likes their logo
It's on everything.

 

[June7]

So either have a 'logo' form that can be embedded on other forms or have a form 'template' that can be copied and then modified for specific use. The first has logo in only one place so easier to replace if modified and also less storage used.

 

[JMongi]

...or have a form 'template' that can be copied and then modified for specific use.

That is what I'm doing. Sorry, if that wasn't clear from the other posts.

This thread was about the labels on a continuous form and making sure there wasn't any Access Form structures I didn't know about. Plus, Access users are creative and I wanted to leave the conversation open ended enough to pull in those out of the box ideas.

Thanks for your input!

 

[Minty]

As per June7 Suggestion, put the logo(s) in a small subform(s).
Only populate the subform object on form load, and you will save a tonne of space on saving the same image over and over.
If the logo changes you only need to update the one form.

I understand what you're saying about labels but there aren't any additional sections available in a form design.

 

[theDBguy]

Just FYI, if you use the Image Gallery, Access will only store the image once, and all your forms can use it. When you update the image, all the forms will automatically reflect that change. You can then save some space by eliminating one subform object from your database.

 

[JMongi]

Just FYI, if you use the Image Gallery...

I assume this is different than linking to a folder location? I was thinking of switching the logo over to a linked image that gets placed in a fixed folder when installed by the user. Of course, that's a lot more work if Access will do the image management for me.

 

[theDBguy]

I assume this is different than linking to a folder location? I was thinking of switching the logo over to a linked image that gets placed in a fixed folder when installed by the user. Of course, that's a lot more work if Access will do the image management for me.

Yes, the Image Gallery stores the files in a system table as Attachments.