Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
|
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 24th, 2003, 01:48 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 129
Thanks: 0
Thanked 0 Times in 0 Posts
Default MSFLXGRD.OCX and MSDATGRD.OCX

I created an application in Access 97. It is a pretty bog standard application using only basic in-built forms, subforms, tables and queries. Nothing fancy.

When I tried to run it on another computer, it produced missing references for MSFLXGRD.OCX and MSDATGRD.OCX. I did not deliberately use these in the development, in fact I cannot see where they are used in the application.

Any ideas how this has happened please?


Clive Astley
__________________
Clive Astley
 
Old July 25th, 2003, 08:47 AM
Registered User
 
Join Date: Jul 2003
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Clive,

I've had a similar problem with MsAccess97. You may want to check the installations of Office on both computers. You can also try repairing the database. My problem was that I built the database on a computer with a newer operating system than the computer I was trying to run it on. I had to go back to the computer I built the database on and save the database again specifying the operating system. This should still be a viable option. If that doesn't work, you may have to print a complete database report and build the database on the computer you want to use. I'd use this as my last resort. You could also check your specific error message with the Microsoft Access97 knowledge base. I'm sure you've tried that, but just in case. It's an option. Hope it works out for you.

am11





Similar Threads
Thread Thread Starter Forum Replies Last Post
Including an .ocx dartcoach VB How-To 9 November 13th, 2006 01:37 PM
Use of NTSVC.OCX jmtoet Pro VB 6 12 June 7th, 2005 05:00 PM
MSCAL.OCX narendrapawar VB Components 0 December 17th, 2004 01:44 PM
mscomct2.ocx CloudNine Access 2 January 15th, 2004 08:12 PM
Use Ocx saulodet ADO.NET 0 January 5th, 2004 01:32 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.