Gina --
OK, here we go, in the order they appear in the list here are the
References:
From usual PC at work where code runs:
Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft DAO 3.6 Object Library
Ole Automation
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Office 11.0 Object Library
Just for grins and giggles I tried the code on a PC at work that has
Access
12. Code runs fiune. Here are the References:
Visual Basic for Applications
Microsoft Access 12.0 Object Library
Microsoft DAO 3.6 Object Library
Ole Automation
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Office 12.0 Object Library
For the PC at home where the code bombs out:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library
Ole Automation
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Office 10.0 Object Library
To my eyes the only difference between PCs is the version of Access
that
is
available. Is it possible there is an incompatability between Access
10
and
any of the other References?
I'm at a total loss.
Any help greatly appreciated.
drb
--
David Burkhart
:
Okay, great!
--
Gina Whipp
"I feel I have been denied critical, need to know, information!" -
Tremors
II
http://www.regina-whipp.com/index.htm
message
Gina --
I'll post the two references after I get home from work Monday --
Need
to
get the one that works from the computer at work.
drb
--
David Burkhart
:
What are the references you have set in the one that works and the
one
that
doesn't work? The code looks fine!
--
Gina Whipp
"I feel I have been denied critical, need to know, information!" -
Tremors
II
http://www.regina-whipp.com/index.htm
message
Gina --
Here's the code. I've left out the declarations.
As part of my testing I've put a break at the first executable
line
of
code
in the function, but I never get to it. As I've said before,
this
code
has
worked perfectly for years on its usual machine which has never
seen
Access
12 so I'm pretty certain the code is OK and the problem is
interaction
with
Access 12.
-----------------
frmSplash, On_Open Event Code
=setstartuptimer()
-----------------
Set Startup Timer Code
Function SetStartUpTimer()
DoCmd.Hourglass True
'Set timer for 6 seconds
Forms![frmSplash].TimerInterval = 6000
'Set default Colors
'gnRGBbaseB = vbWhite
'gnRGBbaseF = vbBlack 'RGB(0, 0, 0) 'Black
'gnRGBeditB = vbRed 'RGB(255, 128, 192) 'Pink
'gnRGBeditF = vbBlack 'RGB(0, 0, 0) 'Black
'gnRGBviewB = vbBlue 'RGB(0, 0, 255) 'Blue
'gnRGBviewF = vbWhite 'RGB(255, 255, 255) 'White
gnRGBbaseB = 16777215
gnRGBbaseF = 0
gnRGBviewB = 16744448
gnRGBviewF = 16777215
gnRGBeditB = 12615935
gnRGBeditF = 0
'Housekeeping done only on startup
'Use presence of username to prevent display of
' frmLogIn when displaying 'About' from help menu
If gcUserName = Empty Then
'Revised 6/17/03 to look for .INI file in
' same folder as the application program mdb
'Set ini name
gcIniName = "COFSwrTrak.INI"
'Set ini location
gcHome = GetDBDir()
gcIniFile = gcHome + gcIniName
'Check database table links
Dim rtnValue As Variant
'Is link value in _.ini ?
Dim cSection As String
Dim cEntry As String
Dim cValue As String
Dim l_Location As String
cSection = Mid(gcIniName, 1, Len(gcIniName) - 4) +
".DataLocation"
cValue = ReadPvtini(cSection, "CurrentData", gcIniFile)
If cValue <> "" Then
' found it, set it up
l_Location = cValue
Else
'mising, force user to find
l_Location = "data"
End If
DoCmd.Hourglass False
'Check database table links
rtnValue = adhVerifyLinks(l_Location, "Report")
'rtnValue = adhVerifyLinks("SwrTrak_Data.Mdb", "Report")
rtnValue = SysCmd(acSysCmdRemoveMeter)
End If 'startup housekeeping
DoCmd.Hourglass False
End Function
-----------
Any ideas greatfully accepted.
drb
--
David Burkhart
:
What is the On_Open code?
--
Gina Whipp
"I feel I have been denied critical, need to know,
information!" -
Tremors
II
http://www.regina-whipp.com/index.htm
in
message
The saga continues.
Running XP Pro, SP3 Build 2600. I downloaded the Allen Browne
discussion
of
Access 10 vs 12 code conflicts on Vista. That seemed to
describe
my
problem
exactly except I am on XP Pro. Implemented Option 1: Modify
Registry.
Tried
to run my Access 10 code and got the same OnOpen error as
before.
Depression set in.
Removed the evaluation version of Office 2007 from the PC;
Allen's
Option
5.
After restart, checked References of my code and found Access
12
no
longer
referenced.
Brighter day.
Tried to run Access 10 code. Failed on same OnOpen error as
before.
Depression, again.
Moved code to a PC that is XP Pro, SP3, Build 2600 that has
never
seen
Office 2007 or Access 12.
Ever hopefull.
Tried to run the code. Failed on same OnOpen error as before.
Checked
References, Access 12 not referenced.
Depression, again.
I would begin to doubt my code except I can take the code to a
PC
at
work
(XP Pro, SP? Build?) and the code runs fine. That PC has
Access
11
(Office
2003) installed.
Ideas anyone? Any help would be appreciated.
drb