Problem with subform recordset

  • Thread starter Thread starter Sebastian
  • Start date Start date
S

Sebastian

Greetings,

I have recently upgraded to Microsoft Office 2003 from
Office 2000. On opening Access, I saw the warnings about
macros and installed the latest Jet service Pack (v8).

I am trying to use a database developed for Access 2000.
Since it is still being developed, I would like to leave
it in Access 2000 format.

The problem is that the recordset on a subform shows the
correct number of records, but all have #Name? in the
fields. The subform's recordsource is a dynamically
created SELECT statement drawing from a SQL pass-through
query. The query works fine and I can see all records if
I open it from the Queries pane.

Meanwhile, the database works fine on a back-up
workstation using Office 2000.

Any thoughts or suggestions gratefully received.
 
I upgraded everything from Office 2000 to Office 2003. Now
I have a major problem. Access 2000 never cared if you
refer to an object as
-----------------------
[Forms]![frmExplorer]![sbfrmGeneric]![cbo_Search]
-----------------------

or as

-----------------------
[Forms]![frmExplorer]![sbfrmGeneric].[Form]![cbo_Search]
-----------------------


but Access 2003 (with 2002-2003 file format) does - so
check your naming references and try using blank query
grids to right-click/"build" a reference to subform
controls, etc.

The extra ".[Form]!" is what the new Access 2003 is
looking for when referencing subforms.
 
Thanks for that. I had a hunt through, but I have been using that syntax
anyway.

In case it helps, I am (on occasion) getting the message '3709 The search
key was not found in any record'. When this happens, the number of records
in the subform is not correct - it retains the number from the previous
parent.

I am setting the subform's recordsource in the parent form and can check to
see that it is valid using the Immediate window - all well there.

Any other thoughts as to what Access 2003 wants to have in a different
syntax?

Thanks and regards

Sebastian
 
Actually - someone showed me a way around this whole
problem:
Reduce the security setting (Tools/Macro/Security...)
to "Low." This makes the naming convention much less
strict. The original reply to my post is below ....

---------------------------------------------------

I had a similar problem. In my case I solved it by
reducing the security setting (Tools/Macro/Security...)
to "Low."

Although a little dangerous, this did get me by my problem
temporally until I can learn more about the whole
certificate thing.

And to put dangerous into perspective. Setting it to low
makes it just like Access 2000 and 2002 which didn't have
any VBA security.

To aid with making global changes which you might end up
having to do in the future, my favorite product is "Find
and Replace" from
Rick Fisher Consulting at http://www.rickworld.com.

Good luck.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
Your reply and assistance is much appreciated. I had already tried setting
the security to low when plagued by endless pop-ups. Nothing seems to work
and I suspect it may be to do with the pass-through query I am using to SQL
Server.

I can't lose more time on this and intend to raise the issue with Microsoft
PSS. If an answer is forthcoming, I will post it here.

Many thanks and regards

Sebastian
 
Back
Top