importing form source code into access

[enrio]

I need to process the source code associated with the forms
outside access, and import the changes back to Access.

I find that I can export the source code of a form, but when I
subsequently import it, even with no change, I get a message saying
the module name is illegal. If the form is named Form_NewPartici pant,
the export file gets named Form_NewPartici pant.cls, and when I reimport
it, the error message quotes the name "Form_NewPartic ipants1.cls",
(notice the digit '1') and says module names may not start "Form_".

The form is not associated with a module (as far as I can understand).
In the project browser, the forms appear in the folder "Microsoft
Access Class Objects", not under the folders Modules or Class Modules.

The top of the export file reads:

VERSION 1.0 CLASS
BEGIN
MultiUse = -1 'True
END
Attribute VB_Name = "Form_NewPartic ipant"
Attribute VB_GlobalNameSp ace = False
Attribute VB_Creatable = True
Attribute VB_PredeclaredI d = True
Attribute VB_Exposed = False

and then follows the code I usually see in the code editor.

I first tried changing the file name, got same message. Then changed
the "Attribute VB_Name" removing the Form_ part, and I got a new class
module, instead of updating the form's code.

I have 43 forms, and having to copy and paste each separately is a
nissance, because I will have to do this frequently.

Any suggestion?

Thanks.

[Arno R]

Enrio,

I need to process the source code associated with the forms
outside access, and import the changes back to Access.

Why do you need to do this ?
You have a Frontend - Backend database don't you?
Why can't you just update the FE?
Or am I missing something here?

But if you *need* to do what you want:
Maybe the undocumented SaveAsText - LoadFromText procedures are what you are looking for?
Check out Google for lots of information about this.
You could export all your forms and write some code to update the changed ones.

--
Hope this helps
Arno R

[Steve Jorgensen]

The problem is that you can't associate code with a form object during import,
so it tries to import the code as a stand-alone module instead. You can get
around this by exporting the entire form object, including the code instead of
just the code. To do this, you use the undocumented "SaveAsText " procedure.
To load the object back in, use "LoadFromTe xt".

Example:
SaveAsText acForm, "frmReportTimeW orkedByDate",
"C:\frmReportTi meWorkedByDate. frm"

In the file that is exported, you can identify the code by looking for the
first line that starts with "CodeBehindForm ". There are some "Attribute ..."
lines after that, and then the VBA code itself begins. The code section is
the last thing in the file, and there is no additional non-VBA content after
it.

On 31 Mar 2005 06:57:58 -0800, en***@online.no wrote:

I need to process the source code associated with the forms
outside access, and import the changes back to Access.

I find that I can export the source code of a form, but when I
subsequently import it, even with no change, I get a message saying
the module name is illegal. If the form is named Form_NewPartici pant,
the export file gets named Form_NewPartici pant.cls, and when I reimport
it, the error message quotes the name "Form_NewPartic ipants1.cls",
(notice the digit '1') and says module names may not start "Form_".

The form is not associated with a module (as far as I can understand).
In the project browser, the forms appear in the folder "Microsoft
Access Class Objects", not under the folders Modules or Class Modules.

The top of the export file reads:

VERSION 1.0 CLASS
BEGIN
MultiUse = -1 'True
END
Attribute VB_Name = "Form_NewPartic ipant"
Attribute VB_GlobalNameSp ace = False
Attribute VB_Creatable = True
Attribute VB_PredeclaredI d = True
Attribute VB_Exposed = False

and then follows the code I usually see in the code editor.

I first tried changing the file name, got same message. Then changed
the "Attribute VB_Name" removing the Form_ part, and I got a new class
module, instead of updating the form's code.

I have 43 forms, and having to copy and paste each separately is a
nissance, because I will have to do this frequently.

Any suggestion?

Thanks.