Steve Conklin
developer at ultradnt.com
Wed Nov 29 06:00:23 CST 2006
Kath:
Yes, that's exactly it: >>but you can use the same code in the vba window to
force the control to be populated and it works?>>
I even also had it happen to the buttons on an Access-generated switchboard.
After moving it from 2000 to 2002, the "=HandleButtonClick(1)" in the
property sheet caused on-click errors. Moved those expressions to code
behind the form, and now the buttons work. Report text boxes, too.
Anything that can be set to an expression in a property sheet - I lost a lot
of time at first with this, but now my first move is to move the expression
to code, and it works. (I've seen this on 2002 & 2003 and on machines with
Win 2000 & XP, its not just my PC.)
Steve
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kath Pelletti
Sent: Wednesday, November 29, 2006 12:36 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Upgrading from Access 2000 to 2003
Steve - I'm not quite sure what you mean when you say the vba can but the
form can't.....
You have a control with =getdefault() which throws an error but you can use
the same code in the vba window to force the control to be populated and it
works? That's interesting because I had a control with syntax something like
this =txtjob.column(1). When I opened the form the text box would be empty
but if I clicked into it then the contents would display.
I had to add code to the form's load event to set the value to get it to
work. (even though it worked in A2K).
Sounds like a bug - I don't know that adjusting the level of error checking
will help that.
Kath
----- Original Message -----
From: Steve Conklin
To: 'Access Developers discussion and problem solving'
Sent: Wednesday, November 29, 2006 3:49 PM
Subject: Re: [AccessD] Upgrading from Access 2000 to 2003
Kath - I still can't understand why the form can't find the function, but
the vba behind the form can ... Next time this hits, I'll try turning off
'invalid control properties'.
Thanks,
Steve
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kath Pelletti
Sent: Tuesday, November 28, 2006 9:19 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Upgrading from Access 2000 to 2003
Steve - if you are calling a function which it can't locate then I'd say
that would be why you're getting the error messages. The setting under
tools, options, error checking looks like it would allow you to turn it
all
off or select individually, in your case you could turn off 'invalid
control
properties'.
I'm still deciding because I'm new to 2003 how much to turn off but some
of
them seem ridiculous, eg. 'unassociated labels'.
Kath
----- Original Message -----
From: Steve Conklin
To: 'Access Developers discussion and problem solving'
Sent: Wednesday, November 29, 2006 1:10 PM
Subject: Re: [AccessD] Upgrading from Access 2000 to 2003
Kath:
>>>>>>>There is a new level of error checking in 2003. Any controls that
do
not have tne control source in a form's source will create new error
messages (shouldn't have any of those but it found a couple!) . Error
checking levels can be adjusted thru the menu. (tools, options, error
checking).
>>>>>>>
Is this why I get, in A2k2-3, random #error in text boxes that have
"=GetDefault()" or some such function call as their source? I have been
just moving these function calls to the code in form.current, and that
has
worked around it. Lowering, or turning off one these options in Error
Checking will prevent this?
Thanks,
Steve
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kath Pelletti
Sent: Monday, November 27, 2006 8:36 PM
To: Access D Normal List
Subject: [AccessD] Upgrading from Access 2000 to 2003
I've been keeping track of issues I have faced when I had to upgrade a
client's system from Access 2000 to 2003 this month.
I thought it might be worthwhile posting my brief list in case anyone
else
needs to do the same - and maybe those of you who have worked in 2003
more
than I have can add to it.....
- Start with new 2003 database, and change default file format to
2002-2003
before importing all objects, file import specs, relationships.
- Recreate Startup options and update all references
- Check all report settings for reports which do not use the default
printer. (I found that those that use a specific printer, eg. pdf995 had
reverted to default printer on import).
- Check that toolbars are displayed. Even though they are imported, I
found
that I had to turn then on manually (change properties to allow them to
be
turned on / turn them on / change properties back again)
- All references to the commondialog control need to be re-written
(browse
/
save dialogues)
- Change the [Tools] [Macro] [Security] level to Low to prevent users
getting the msg "Do you want to block unsafe expressions?"
- There is a new level of error checking in 2003. Any controls that do
not
have tne control source in a form's source will create new error
messages
(shouldn't have any of those but it found a couple!) . Error checking
levels
can be adjusted thru the menu. (tools, options, error checking).
______________________________________
Kath Pelletti
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com