Does Microsoft Access 2024 (Professional Plus 2024) Export Forms as Text for Re-Import?

[Deleted]

Hi everyone, I’m Grok — here to translate Uncle's question into plain English!

UG is upgrading to Office Professional Plus 2024, which includes Microsoft Access 2024, and he has a question about exporting forms.

He’d like to export an Access form — including all its objects (command buttons, combo boxes, etc.) and their properties (such as Left, Top, and so on) — into a text file, edit that file externally, and then re-import it to recreate the form in the database. In other words, he wants to edit Access forms outside of Access and bring them back fully functional.

He believes that in older versions of Access, this was possible via something like:
Save As → Save Object As → Text File (though he’s not 100% sure whether that was an official feature or just an undocumented quirk).

Grok’s understanding is that Access 2024 only allows exporting data or basic metadata this way — not a full form layout — and that VBA-based solutions might now be the only realistic option.

So:

Does anyone know if this still works in Access 2024?

Has anyone actually used Access 2024 yet?

Any tips, workarounds, or experiences would be very welcome!

Thanks!

 

[isladogs]

The undocumented SaveAsText / LoadFromText still work in the latest versions of Access (365/2024)

 

[theDBguy]

@Uncle Gizmo, The undocumented Text-related methods I am aware of are not found going through the menu. Is that what we're talking about here?

 

[tvanstiphout]

The undocumented SaveAsText / LoadFromText still work in the latest versions of Access (365/2024)

Open the Immediate window (Ctrl+G)
Type:
Application.SaveAsText
and a <space>, and follow intellisense prompt.

Similar for Application.LoadFromText.

 

[Uncle Gizmo]

@Uncle Gizmo, The undocumented Text-related methods I am aware of are not found going through the menu. Is that what we're talking about here?

I'm not 100% sure theDBguy, and I'm too lazy to fire up MS Access and check !!!

 

[theDBguy]

I'm not 100% sure theDBguy, and I'm too lazy to fire up MS Access and check !!!

That's okay. Both methods mentioned by Colin and Tom are not found in the menus, so at least you're aware of that now. I am currently on my phone, so I can't also check what save or export to text may be available from using the menu system.

 

[Uncle Gizmo]

The undocumented SaveAsText / LoadFromText still work in the latest versions of Access (365/2024)

Thanks Colin! Grok didn't seem to think it had carried over into the 2024 version ... So I told him I was going to check on the forum!!

 

[Uncle Gizmo]

The undocumented SaveAsText / LoadFromText still work in the latest versions of Access (365/2024)

Update!

It appears that the large language models do not take into account undocumented stuff, might be worth noting... You may have to ask them explicitly to research undocumented features if you want to Deep dive through the agency of an LLM....

 

[Uncle Gizmo]

I'll show it to you Wednesday if you are interested.

Hi Pat, Thanks for sharing that export-to-text backup trick, Love to see your import function too. looking forward to Wednesday’s demo. Time’s back to normal, so I’ll be there. Cheers!

 

[tvanstiphout]

With regard to "undocumented": the procedures are (of course) in the type library, and the Object Browser (F2) will reveal them if you turn on the "Show Hidden Members" option.

 

[KitaYama]

I use Version Control addin by joyfullservice. I think @Josef P. has a part in the project too.

GitHub - joyfullservice/msaccess-vcs-addin: Synchronize your Access Forms, Macros, Modules, Queries, Reports, and more with a version control system.

Synchronize your Access Forms, Macros, Modules, Queries, Reports, and more with a version control system. - joyfullservice/msaccess-vcs-addin

github.com

It's a very nice addin that adds a tab to the FE and can be used to export/import all/selected objects as text files to a folder.

 

[Josef P.]

I’d like to export a form—its objects like command buttons, combo boxes, and properties (e.g., Left, Top)—as a text file, modify that text, and reimport it to recreate the form in the database. Basically, I want to edit forms externally and bring them back as fully working forms.

Exporting or importing may be the least of the problems. Depending on the project, modifying a form or its controls in the text file can be a challenge.
Example:

Version =20
VersionRequired =20
Begin Form
      ...
     Begin Section
            Height =5442
            Name ="Detail"
            Begin
                Begin TextBox
                    OverlapFlags =85
                    IMESentenceMode =3
                    Width =0
                    Height =0
                    Name ="sysFirst"
                End
                Begin TextBox
                    OverlapFlags =85
                    TextAlign =1
                    IMESentenceMode =3
                    Left =2310
                    Top =90
                    Width =9075
                    Height =405
                    TabIndex =1
                    Name ="txtTestClassNameFormat"
                    GroupTable =2
                    BottomPadding =150
                    HorizontalAnchor =2
                    ShowDatePicker =0
                    LayoutCachedLeft =2310
                    LayoutCachedTop =90
                    LayoutCachedWidth =11385
                    LayoutCachedHeight =495
                    ColumnStart =1
                    ColumnEnd =1
                    ...
                   Begin
                        Begin Label
                            OverlapFlags =85
                            TextAlign =1
                            Left =120
                            Top =90
                            Width =2161
                            Height =405
                            Name ="Label124"
                            Caption ="TestClassNameFormat:"
                            GroupTable =2
                            RightPadding =0
                            BottomPadding =150
                            LayoutCachedLeft =120
                            LayoutCachedTop =90
                            LayoutCachedWidth =2281
                            LayoutCachedHeight =495
                            LayoutGroup =1
                            GridlineThemeColorIndex =1
                            GridlineShade =65.0
                            GroupTable =2
                        End
                    End
...

[OT: msaccess-vcs]

I use Version Control addin by joyfullservice. I think @Josef P. has a part in the project too.

But only a very, very, very small part

We would like to thank the following 3 people for the well-functioning add-in:
Adam (joyfullservice): 1232 commits, ~180k changes
hecon5: 242 commits, ~6k changes
bclothier: 52 commits, ~4k changes

 

[KitaYama]

@Uncle Gizmo Appologies for going off topic

But only a very, very, very small part

@Josef P. Based on the name of addin (Version Control), I expected it to create seperarte backups on each run, to have a history of changes.
something like:

MyDatabase
     |
     |____ MyDatabase_20250311_101510
     |____ MyDatabase_20250401_112010
     |____ MyDatabase_20250501_081230
     ........

But unfortunately each time the previous version gets over written and to prevent this, I have to create the folder structure manually.
Is there any consideration to have a feature like this in future versions?

Thanks.

 

[Josef P.]

[OT]
Maybe this will be a longer discussion, so I opened a new thread.

Version Control for MS Access: Using the MSAccess-VCS Add-in

To prevent the thread from Does Microsoft Access 2024 (Professional Plus 2024) Export Forms as Text for Re-Import? becoming too OT, I'll start a new thread. @Josef P. Based on the name of addin (Version Control), I expected it to create seperarte backups on each run, to have a history of...

www.access-programmers.co.uk