Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / May 2005

Tip: Looking for answers? Try searching our database.

File format no longer supported

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Connie Briggs - 03 May 2005 18:44 GMT
I have taken over the development of a new Access applicaiton from a
programmer. (my area is database design, not programming)

In order to salvage the application when the file became corrupted earlier,
I created a blank database and imported all of my objects into it. After
that, I had to go to Tools/References and select 'Microsoft DAO 3.6 Object
Library' to get over a problem with the code not recognizing some of the
previous developer's datatypes. Now it is no longer recognizing 'Now()' in
the reports, so I looked through the list of available references, but
nothing jumped out at me as an obvious solution, however, I have 3 problems
now. In addition to 'Now()' not producing the current date in my reports,
when I open my file, I now get an error message 'File format no longer
supported' and 'invalid data type' when I select some of my command buttons
to open forms. I am afraid that the cause may have been my accidentally
clicking on VBA as a reference, when I was scrolling through the list. I
accidentally unchecked it, but it gave me a message that it could not be
removed. It remained checked, but the new problem started then.

This may be unrelated, but before I got the 'File format no longer
supported' error, I was unable to synchronize with my replica.

Is there any way to fix this? I have an earlier version that the IT dept.
can restore, but that would mean losing a full day's development.
Van T. Dinh - 03 May 2005 23:14 GMT
It sounds like corruptions to me.

Try a few methods outlineed by Tony Toews:

http://www.granite.ab.ca/access/corruptmdbs.htm

Signature

HTH
Van T. Dinh
MVP (Access)

> I have taken over the development of a new Access applicaiton from a
> programmer. (my area is database design, not programming)
[quoted text clipped - 19 lines]
> Is there any way to fix this? I have an earlier version that the IT dept.
> can restore, but that would mean losing a full day's development.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.