Hi!  Call me Eun.  



We keep our Access file in the network so that people can share front-end 

files (1).  When I tried to Compact and Repair those Access files, it 

always failed, and gave me an error message:



"Counld not find field 'Description'"



But some files do even have a field named 'Description'.



Can someone explain possible reasons for this error, and also possible 

solutions to compact and repair Access files stored in the netwrok.



(1) I decided to keep front-end files in the network first, because the 

report we generate has calculated fields from queries, and I did not feel 

comfortable to risk the danger of generating different values in those 

calculated fields for the same reports that people uses.  Okay, if this is 

not a good reason, hear this.  Second, job changes are happening all the 

time in my office, so it is a simpler way to keep track of all database 

files in one place--netwrok.  Third, if we have to make changes, then I 

have to ask people to copy new front end files to their local workstation, 

but in the network, I can just make changes, and people do have to do 

anything, except using it as they have been.  



So I think I have good and legitimate reasons to keep Access files in the 

network.  Please help me!



Eun

Sounds like corruption--have you tried creating a blank mdb and then

importing all your objects into it?  If you can do that without difficulty,

can you compact/repair the copy?



BTW, there's nothing wrong with keeping front-end files on the server--no

need to justify that decision, in my opinion...



Cheers,



-Roy



-----Original Message-----

From: Eun Namkung [mailto:matvei27@y...]

Sent: Tuesday, August 21, 2001 8:35 AM

To: Access

Subject: [access] compact and repair Access file stored in network





Hi!  Call me Eun.  



We keep our Access file in the network so that people can share front-end 

files (1).  When I tried to Compact and Repair those Access files, it 

always failed, and gave me an error message:



"Counld not find field 'Description'"



But some files do even have a field named 'Description'.



Can someone explain possible reasons for this error, and also possible 

solutions to compact and repair Access files stored in the netwrok.



(1) I decided to keep front-end files in the network first, because the 

report we generate has calculated fields from queries, and I did not feel 

comfortable to risk the danger of generating different values in those 

calculated fields for the same reports that people uses.  Okay, if this is 

not a good reason, hear this.  Second, job changes are happening all the 

time in my office, so it is a simpler way to keep track of all database 

files in one place--netwrok.  Third, if we have to make changes, then I 

have to ask people to copy new front end files to their local workstation, 

but in the network, I can just make changes, and people do have to do 

anything, except using it as they have been.  



So I think I have good and legitimate reasons to keep Access files in the 

network.  Please help me!



Eun

It works now.  Thanks.



Eun



> Sounds like corruption--have you tried creating a blank mdb and then

> importing all your objects into it?  If you can do that without 

difficulty,

> can you compact/repair the copy?

> 

> BTW, there's nothing wrong with keeping front-end files on the server--no

> need to justify that decision, in my opinion...

> 

> Cheers,

> 

> -Roy

> 

> -----Original Message-----

> From: Eun Namkung [mailto:matvei27@y...]

> Sent: Tuesday, August 21, 2001 8:35 AM

> To: Access

> Subject: [access] compact and repair Access file stored in network

> 

> 

> Hi!  Call me Eun.  

> 

> We keep our Access file in the network so that people can share front-

end 

> files (1).  When I tried to Compact and Repair those Access files, it 

> always failed, and gave me an error message:

> 

> "Counld not find field 'Description'"

> 

> But some files do even have a field named 'Description'.

> 

> Can someone explain possible reasons for this error, and also possible 

> solutions to compact and repair Access files stored in the netwrok.

> 

> (1) I decided to keep front-end files in the network first, because the 

> report we generate has calculated fields from queries, and I did not 

feel 

> comfortable to risk the danger of generating different values in those 

> calculated fields for the same reports that people uses.  Okay, if this 

is 

> not a good reason, hear this.  Second, job changes are happening all the 

> time in my office, so it is a simpler way to keep track of all database 

> files in one place--netwrok.  Third, if we have to make changes, then I 

> have to ask people to copy new front end files to their local 

workstation, 

> but in the network, I can just make changes, and people do have to do 

> anything, except using it as they have been.  

> 

> So I think I have good and legitimate reasons to keep Access files in 

the 

> network.  Please help me!

> 

> Eun