Creating new form instance in Access 2003 SP3

[Guest]

I have had a database working for 3 years that creates multiple instances of
a main data form. It uses the idea of:

Dim frm as Form
set frm = new Form_frmCall

and then add the form reference to a collection to keep it active.

It worked until SP3. Now the Set statement fails with error 2950, Reserved
Error.

Is this functionality going away?

Thanks,

 

[Allen Browne]

Kevin, I'm not seeing that problem.

The sample database in this page still works in A2003 SP3:
http://allenbrowne.com/ser-35.html

 

[Guest]

Sure enough! The sample works just fine. With just a little egg on my face,
I note that I am not able to open the target form in Design View; it tells me
that there isn't enough memory.

It is a very large form with a tab bar and multiple subforms. I see that
you have already reported this to Microsoft under a different thread. Plus,
I am using SourceSafe integration, ODBC links to Oracle, and MDEs. I guess
I'm doing my best to make myself a Service Pack Target.

OUCH! This means that my problem is not fixable by stripping the
multi-instance option. Glad I found this out before doing it. (sigh)

Thanks,

Kevin

 

[Guest]

Little more information. I managed to convert the database to Access 2000
format, removing the link to source control. Then, I converted back to
2002/2003 format, and the forms work now. So, could the issue be related to
the COM changes in SP3 interfering with certain functions of the SourceSafe
add-in? It only halted on some forms, including 1 subform with several
comboboxes and more than 10 text fields. Coincidence?

Kevin

 

[Allen Browne]

Given that you rescued the file by converting to a different version and
back, there may have been some corruption in the file. The process would
have dumped some kinds of corruption.

Alternatives may have been a decompile (to dump the binary and have Access
recreate it.) Or perhaps it could have been rescued with the undocumented
SaveAsText (to save the form as a text file), delete, compact, LoadFromText
(to reimport it.) But since this form had several subforms, you may have
needed to do this to the subforms as well, until you identified the culprit.
Even the linking between the main- and subforms could have been suspect.

I actually had a client with one of these this week. The corrupt form (or
possibly subform(s)) failed with "Not enough memory error", and the usual
tricks (as above) didn't work. We ended up programmatically correcting the
properties of the tables and fields, compacting, importing them into a new
database, importing the queries, and re-creating this form and its subforms
(pasting in the code from Notepad so it didn't have to be re-written.)

That was on A2003 SP3. No SourceSafe.

 

[tmc21ster]

I am having the same problem after updating to O2003 SP3. When trying
to create the Access MDB from VSS, I continually get "The search key
was not found in any record" followed by the "Failed to import file
'yada yada'". My colleagues that are also working on the same 20 odd
MS Access 2003 projects in VSS (using A2003 SP2) are not having any
problems creating from VSS).

As has been sugessted elsewhere (http://kbalertz.com/927680/Error-
message-create-database-Visual-SourceSafe-project-Access-Access-
import.aspx), I have verified that my default DB format is A2002 -
2003 format (Tools>Options>Advanced).

HELP!

 

[jkiefer580]

I had the same problem as Kevin. I had an adp created with A2003 SP2
and under souce control with the Source Safe add-in. It was working
great in SP2, then I installed SP3 and started getting the memory
error opening every form but one. I ended up taking the adp out of
souce control, opening it in A2003 SP2, and exporting every object
into a blank adp. It then started working fine in SP3, though I
stopped using the Source Safe add-in, which is a shame as I had just
started using it a month ago and was really digging it.

Joe