J
John Cambridge
Just updated to Access 2007 on network with 10 users gettign owc error.
Normal corrections in Access 2002 etc have not worked
Normal corrections in Access 2002 etc have not worked
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Gina Whipp
John,
You didn't mention what are those *normal corrections* were... I would
uncheck that reference and compile. See the bottom of the page...
http://www.regina-whipp.com/index_files/References.htm
--
Gina Whipp
2010 Microsoft MVP (Access)
"I feel I have been denied critical, need to know, information!" - Tremors
II
http://www.regina-whipp.com/index_files/TipList.htm
Just updated to Access 2007 on network with 10 users gettign owc error.
Normal corrections in Access 2002 etc have not worked
You didn't mention what are those *normal corrections* were... I would
uncheck that reference and compile. See the bottom of the page...
http://www.regina-whipp.com/index_files/References.htm
--
Gina Whipp
2010 Microsoft MVP (Access)
"I feel I have been denied critical, need to know, information!" - Tremors
II
http://www.regina-whipp.com/index_files/TipList.htm
Just updated to Access 2007 on network with 10 users gettign owc error.
Normal corrections in Access 2002 etc have not worked
A
a a r o n _ k e m p f
If I want to use OWC in Office 2007, I just download and install OWC
2003 and then OWC 2002
Somethign about that combination (and order) has fixed every problem
I've ever had.
PS - OWC ships on about a half dozen Microsoft products right now.. so
it's not a question of 'having owc' it's about having it licensed for
dynamic use.
The best way I've done that is install Office 2007, SQL 2005/2008
(which definitely has OWC in it), OWC 2003, OWC 2002
installing OWC 2002 gets rid of the licensing problem for some reason
(from what I've experienced firsthand)
I love OWC.
I can name two large companies in Seattle-- that aren't Microsoft--
that each have 70,000 OWC reports.
Microsoft stranded them.
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
2003 and then OWC 2002
Somethign about that combination (and order) has fixed every problem
I've ever had.
PS - OWC ships on about a half dozen Microsoft products right now.. so
it's not a question of 'having owc' it's about having it licensed for
dynamic use.
The best way I've done that is install Office 2007, SQL 2005/2008
(which definitely has OWC in it), OWC 2003, OWC 2002
installing OWC 2002 gets rid of the licensing problem for some reason
(from what I've experienced firsthand)
I love OWC.
I can name two large companies in Seattle-- that aren't Microsoft--
that each have 70,000 OWC reports.
Microsoft stranded them.
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
OWC should be open-sourced without limits!!!!!!!!!!!!!!!!!!
D
De Jager
John Cambridge said:Just updated to Access 2007 on network with 10 users gettign owc error.
Normal corrections in Access 2002 etc have not worked