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 / Conversion / May 2004

Tip: Looking for answers? Try searching our database.

Conversion-related problem?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mable - 27 May 2004 20:54 GMT
Greetings,
My company currently uses Office 2000, with the exception
of Access, which they still use as 97. I inquired into
this discrepancy and found that it is because they were
having problems with converting 97 databases into 2000
versions.

Unable to believe that Microsoft would release a product
that wasn't capable of handling files from it's direct
ancestor, I set to work trying this conversion for myself.
As expected, there were no immediate errors.

I came across a problem through more extensive testing,
however. It seems that I cannot save anything I write to
the converted databases. When I enter new records, either
through the application FE or through direct entry, and
click save, the information does not stay saved.

Can anyone shed some light on this problem?
-Mable
Albert D. Kallal - 27 May 2004 21:40 GMT
> I came across a problem through more extensive testing,
> however. It seems that I cannot save anything I write to
[quoted text clipped - 4 lines]
> Can anyone shed some light on this problem?
> -Mable

Hum, that is very strange indeed. Was their any copying of the file(s) to a
cd rom/burner in the transfer? a cd-rom (Read Only Memory) converts files to
a read only format (that is why they are called "rom" which means
ReadOnlyMemory).

If you then copy the files from that CD to your computer..they are still
flagged as read only. You have to right click on the files, and un-select
the "read only" setting.

I suppose it is possible that you are doing this on some server based
system, and perhaps the directory's were you are working you don't have
correct permissions.

However, if the conversion went ok..then I see little, or no reason why the
newer stuff don't work.

Do the files works on your local pc? If they are a linked system, then you
have to use the linked table manger to change the location, or even if just
the name of the files are changed, then linked table manger need to be used,
else you will actually be updating the original back end files!

So, check some of the above things...

Signature

Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn

Mable - 28 May 2004 12:31 GMT
To conduct my experiment, I copied, via a "Map Network
Drive" connection, three databases commonly used by the
staff. At no time was any of it placed upon a cdRom.

I think, had it been flagged as Read-Only, Access would've
complained.

Everything (database, FE, tables, etc) is currently on my
local machine.

I appreciate the input.

Any other ideas?
-Mable
>-----Original Message-----
>
[quoted text clipped - 29 lines]
>
>So, check some of the above things...
Albert D. Kallal - 28 May 2004 20:32 GMT
Hum,

Did you run the linked table manger...and re-link the FE to the BE?

Signature

Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn

 
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.