problems after converting from 97 to 2003

[×די]

i was using a great program someone once built for me in access 97.
eversince i upgraded to office 2003 and converted the program to access 2003
and the database also my reports are not working. i need help!
is there maybe something i can download that will convert from 97 to 2003 in
a better way?

 

[Douglas J. Steele]

Sorry, but "not working" doesn't give us much to go by.

Are you getting any error messages? If so, what are they?

 

[×די]

ok
i get this message :
" you entered an expression that has an invalid reference to the property
Visible"
" the property may not exsit or may not apply to the object you specified"

it's refered to a macro that suppose to set values from a from to a query
and based on this to create the wanted report.

i didnt touch anything. i just converted to 2003. in access 97 it still
works but in 2003 it doesnt. any ideas?

 

[Douglas J. Steele]

How does the macro refer to the control that it's trying to toggle?

 

[×די]

i dont know. the macro is running after i'm pressing the button.
it's built from two parts
1 :
SetValue :
Item - [visible]
Expression - Yes
2:
OpenReport :
ReportName - Worker_report
View : Print Preview

 

[Douglas J. Steele]

What's Visible then? I'd assumed you were trying to make a control visible
(or invisible). Is Visible the name of a control (or field) instead? If so,
rename it: Visible is a reserved word, and running into problems when you
use reserved words for your own purposes is common.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

i dont know. the macro is running after i'm pressing the button.
it's built from two parts
1 :
SetValue :
Item - [visible]
Expression - Yes
2:
OpenReport :
ReportName - Worker_report
View : Print Preview

How does the macro refer to the control that it's trying to toggle?

 

[×די]

no,there is no such control in the form nor in the report. i dont know what
the other programmer did with it but on 97 it works.
is it possible that there r changes between 97 to 2003 that prevent from old
code sytanxes to work? or that there is some difference in developing with 97
and 2003?
maybe i'll have to create the reports again under 2003?
i guess there r stuff that cannot be fully converted succsefully from 97 to
2003. am i right?

What's Visible then? I'd assumed you were trying to make a control visible
(or invisible). Is Visible the name of a control (or field) instead? If so,
rename it: Visible is a reserved word, and running into problems when you
use reserved words for your own purposes is common.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

i dont know. the macro is running after i'm pressing the button.
it's built from two parts
1 :
SetValue :
Item - [visible]
Expression - Yes
2:
OpenReport :
ReportName - Worker_report
View : Print Preview

How does the macro refer to the control that it's trying to toggle?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



ok
i get this message :
" you entered an expression that has an invalid reference to the
property
Visible"
" the property may not exsit or may not apply to the object you
specified"

it's refered to a macro that suppose to set values from a from to a
query
and based on this to create the wanted report.

i didnt touch anything. i just converted to 2003. in access 97 it still
works but in 2003 it doesnt. any ideas?


:

Sorry, but "not working" doesn't give us much to go by.

Are you getting any error messages? If so, what are they?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



i was using a great program someone once built for me in access 97.
eversince i upgraded to office 2003 and converted the program to
access
2003
and the database also my reports are not working. i need help!
is there maybe something i can download that will convert from 97 to
2003
in
a better way?

 

[Douglas J. Steele]

I've heard of few problems converting. Yes, Access 2003 is stricter in its
syntax, but it normally catches that during conversion.

You might want to download and run the Access 2003 Conversion Toolkit
http://www.microsoft.com/downloads/...76-5d89-450a-b977-980a9841111e&DisplayLang=en

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

no,there is no such control in the form nor in the report. i dont know
what
the other programmer did with it but on 97 it works.
is it possible that there r changes between 97 to 2003 that prevent from
old
code sytanxes to work? or that there is some difference in developing with
97
and 2003?
maybe i'll have to create the reports again under 2003?
i guess there r stuff that cannot be fully converted succsefully from 97
to
2003. am i right?

What's Visible then? I'd assumed you were trying to make a control
visible
(or invisible). Is Visible the name of a control (or field) instead? If
so,
rename it: Visible is a reserved word, and running into problems when you
use reserved words for your own purposes is common.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

i dont know. the macro is running after i'm pressing the button.
it's built from two parts
1 :
SetValue :
Item - [visible]
Expression - Yes
2:
OpenReport :
ReportName - Worker_report
View : Print Preview


:

How does the macro refer to the control that it's trying to toggle?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



ok
i get this message :
" you entered an expression that has an invalid reference to the
property
Visible"
" the property may not exsit or may not apply to the object you
specified"

it's refered to a macro that suppose to set values from a from to a
query
and based on this to create the wanted report.

i didnt touch anything. i just converted to 2003. in access 97 it
still
works but in 2003 it doesnt. any ideas?


:

Sorry, but "not working" doesn't give us much to go by.

Are you getting any error messages? If so, what are they?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



i was using a great program someone once built for me in access
97.
eversince i upgraded to office 2003 and converted the program to
access
2003
and the database also my reports are not working. i need help!
is there maybe something i can download that will convert from 97
to
2003
in
a better way?

 

[Chris Mills]

I can't myself quite understand the macro item 1 (or why it's there):
1 :
SetValue :
Item - [visible]
Expression - Yes

This appears to set the property of "some object" to Visible. That is (or was)
unquestionably it's purpose.

The "macro item 2" just opens a report. I can't imagine why it would need any
"macro pre-processing".

Things I would think of are:
-if it works in A97, are you sure it reads the same there? A97 (in particular)
can suffer from subtle corruptions and therefore may not convert well (unless
"cleaned-up" before conversion).
-What is that line for? Don't ask us, you've taken over maintenance of the
program, and are the only one who has the full program. What happens if you
remove it (in A97?). You will surely soon discover if it was necessary or not!
-Most "legacy programs" ie taken over from someone else, have some level of
claptrap and aborted ideas left in them? (Well, mine do)
-Visible is a property of many objects to make them visible or not. It is not
a word the programmer should use otherwise (being a reserved word with a clear
meaning). For all I know, it could be intended to make SOMETHING invisible in
the "calling menu or system" rather than the called report. It is unlikely to
refer to a report yet to be opened.
-It is unlikely a "Visible" property would prevent things from working (if you
just take it out). The error message says the object it refers to is no longer
available, which I would tend to believe. As to what object, how would we
know, in YOUR database? I tend to think the error message means what it says
(for once!)

You're really not asking an Access question. You're asking how your database
was designed. If you don't know then we sure don't!
(I have covered why things may work in A97 and not in a conversion, at least,
one of the common reasons)

If your code is anything like your spelling (sytanxes), then best take a deep
breath! And start "debugging" step-by-step as any normal programmer would do.
It is NOT a known Access problem, apparently. I would expect, on any
conversion, to have to do some extensive testing. Who knows what bugs may lurk
there? eg, SP-What?
Chris