Computer Change - Database Acting Up

[magmike]

I've moved my database to a new computer. Now a couple of things are
working right. I checked the References in the Module, but nothing
shows up as missing, and as far as I know, the Windows OS and the
Access versions are the same.

Is there something else I could look for?

Thanks in advance.

magmike

 

[Douglas J. Steele]

What problem(s) are you encountering?

 

[magmike]

What problem(s) are you encountering?

--
Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele
(no private e-mails, please)









- Show quoted text -

(1) There is an unbound field ([Summary]) on a subform
([ContactDetails]) that displays the contents of the record selected
on another subform ([ContactListing]) which is a continuous form
related to the record on the master form ([Prospects]) that worked
correctly before I moved the database. Now, for some reason it does
not display any contents at all, as if it can't relate itself to the
selected subrecord (the contact). The data source of the [Summary]
field in the second subform ([ContactDetails]) is a long IF statement
that has always worked and has not been changed. The datasource of
each subform ([ContactDetails] and [ContactListing]) is the [Contact]
table, which has a Many-to-One relationship with the main table,
[Prospects].

(2) Also, there is another field on the master form ([Prospects]),
that used a field ([EMP SIZE]) from another subform ([RefUSA]) that is
on a tab and whose data source is the table [RefUSA] which has a One-
To-One relationship with the master table [Prospects].

 

[Douglas J. Steele]

Are you sure there isn't a difference in service packs between the machines?

Are you sure that your references to the subform are correct? The correct
reference is
Forms![NameOfParentForm]![NameOfSubformControlOnParentForm].Form![NameOfControlOnSubform]

or

Me![NameOfSubformControlOnParentForm].Form![NameOfControlOnSubform].

(It's common to forget the .Form, or to use the name of the form being used
as a subform rather than the name of the subform control. A difference in
service packs may have made a difference in how stringently the syntax rules
are being enforced.)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



(1) There is an unbound field ([Summary]) on a subform
([ContactDetails]) that displays the contents of the record selected
on another subform ([ContactListing]) which is a continuous form
related to the record on the master form ([Prospects]) that worked
correctly before I moved the database. Now, for some reason it does
not display any contents at all, as if it can't relate itself to the
selected subrecord (the contact). The data source of the [Summary]
field in the second subform ([ContactDetails]) is a long IF statement
that has always worked and has not been changed. The datasource of
each subform ([ContactDetails] and [ContactListing]) is the [Contact]
table, which has a Many-to-One relationship with the main table,
[Prospects].

(2) Also, there is another field on the master form ([Prospects]),
that used a field ([EMP SIZE]) from another subform ([RefUSA]) that is
on a tab and whose data source is the table [RefUSA] which has a One-
To-One relationship with the master table [Prospects].

 

[magmike]

Are you sure there isn't a difference in service packs between the machines?

Are you sure that your references to the subform are correct? The correct
reference is
Forms![NameOfParentForm]![NameOfSubformControlOnParentForm].Form![NameOfCon­trolOnSubform]

or

Me![NameOfSubformControlOnParentForm].Form![NameOfControlOnSubform].

(It's common to forget the .Form, or to use the name of the form being used
as a subform rather than the name of the subform control. A difference in
service packs may have made a difference in how stringently the syntax rules
are being enforced.)

--
Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele
(no e-mails, please!)



(1) There is an unbound field ([Summary]) on a subform
([ContactDetails]) that displays the contents of the record selected
on another subform ([ContactListing]) which is a continuous form
related to the record on the master form ([Prospects]) that worked
correctly before I moved the database. Now, for some reason it does
not display any contents at all, as if it can't relate itself to the
selected subrecord (the contact). The data source of the [Summary]
field in the second subform ([ContactDetails]) is a long IF statement
that has always worked and has not been changed. The datasource of
each subform ([ContactDetails] and [ContactListing]) is the [Contact]
table, which has a Many-to-One relationship with the main table,
[Prospects].

(2) Also, there is another field on the master form ([Prospects]),
that used a field ([EMP SIZE]) from another subform ([RefUSA]) that is
on a tab and whose data source is the table [RefUSA] which has a One-
To-One relationship with the master table [Prospects].

You make two very great points. I checked the version and there is not
a Service Pack on their office installation. Also, I wasn't aware of
the subform reference format (i had wondered before - but since it
worked, it never got discovered) and is likely the source of the
difference without the SP. I'll update after getting the SP.

 

[magmike]

Are you sure there isn't a difference in service packs between the machines?

Are you sure that your references to the subform are correct? The correct
reference is
Forms![NameOfParentForm]![NameOfSubformControlOnParentForm].Form![NameOfCon­­trolOnSubform]

or

Me![NameOfSubformControlOnParentForm].Form![NameOfControlOnSubform].

(It's common to forget the .Form, or to use the name of the form being used
as a subform rather than the name of the subform control. A difference in
service packs may have made a difference in how stringently the syntax rules
are being enforced.)

news:61497dce-cc8c-4b34-8013-7848610e5ae4@f63g2000hsf.googlegroups.com...

(1) There is an unbound field ([Summary]) on a subform
([ContactDetails]) that displays the contents of the record selected
on another subform ([ContactListing]) which is a continuous form
related to the record on the master form ([Prospects]) that worked
correctly before I moved the database. Now, for some reason it does
not display any contents at all, as if it can't relate itself to the
selected subrecord (the contact). The data source of the [Summary]
field in the second subform ([ContactDetails]) is a long IF statement
that has always worked and has not been changed. The datasource of
each subform ([ContactDetails] and [ContactListing]) is the [Contact]
table, which has a Many-to-One relationship with the main table,
[Prospects].

(2) Also, there is another field on the master form ([Prospects]),
that used a field ([EMP SIZE]) from another subform ([RefUSA]) that is
on a tab and whose data source is the table [RefUSA] which has a One-
To-One relationship with the master table [Prospects].

You make two very great points. I checked the version and there is not
a Service Pack on their office installation. Also, I wasn't aware of
the subform reference format (i had wondered before - but since it
worked, it never got discovered) and is likely the source of the
difference without the SP. I'll update after getting the SP.- Hide quoted text -

- Show quoted text -

Yep - updated to the SP3 at officeupdate.com and now magically they
both work.