ACCESS FEED: Re: [MS_AccessPros] #deleted in a field value

Sabtu, 27 April 2013

Re: [MS_AccessPros] #deleted in a field value

Hi Bill

The sad situation is that the database is not split, it's just one file on a server. Two people use it during the day by using Access to open the mdb file. The first person to open the database will create the lock file - I'm not sure what happens when the next person opens the database (whilst the first person is still using it). Another aspect is that one person in India connects to the server overnight and does some data input.

I've suggested that the database be split but so far have been met with "Why? Everything's working and not causing a problem" - well now, perhaps it is. Especially as one of the errors says that an update cannot be done because someone else is updating - yet there is only one person using the database.

If I split the database for them (data on server, forms etc on clients) will the first person to open the database still create a lock file and be the "owner" or does it work differently? I know that splitting a database is good practice but can you give me any pointers to the types of problems splitting solves?

Many thanks
Ray

--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Ray
> >I don't think that an index was removed in this case because the
> >users wouldn't
> >know how to. However, it is more likely that there was a network
> >problem -
> >apparently that happens occasionally.
>
> I agree. Do you have the database in a split configuration with the tables on a server and the forms, reports, queries etc on the users' local drive? That would immensely reduce future corruption...at least as far as the forms and queries are concerned .
>
> Bill
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "Ray" <rayfrew@> wrote:
> >
> > Hi Roberto
> >
> > I don't think that an index was removed in this case because the users wouldn't know how to. However, it is more likely that there was a network problem - apparently that happens occasionally.
> >
> > Things have moved forward now, because the database has been recovered from a backup, data is being rekeyed and another backup is about to be taken. Probably best to take more than one eh?
> >
> > Thanks for your help.
> > Ray
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "RobertoARV" <robertoarv@> wrote:
> > >
> > > Sometimes when it happens , an index is removed, then you need to delete
> > > records showing deleted# mark , run a compact database , recreate the index
> > > and then create a blank database and import all objects from fixed
> > > database.
> > >
> > >
> > >
> > > From: MS_Access_Professionals@yahoogroups.com
> > > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of RobertoARV
> > > Sent: Thursday, April 25, 2013 11:28 AM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > Subject: RE: [MS_AccessPros] #deleted in a field value
> > >
> > >
> > >
> > >
> > >
> > > I have seen this for years with this database , often happens when you
> > > migrate same database to another upper version, you need to install all the
> > > Microsoft jet service patches. it also occurs when you edit same record in 2
> > > computers , it shows deleted in other computer but it get fix when you run a
> > > requery in form or simply close form and open it again. it happens too when
> > > a network disconnect occurs when you are editing a record.
> > >
> > > From: MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > [mailto:MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Bill Mosca
> > > Sent: Thursday, April 25, 2013 9:39 AM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > Subject: RE: [MS_AccessPros] #deleted in a field value
> > >
> > > Ray
> > >
> > > The most likely cause is a corrupted index. It might have been saved if you
> > > imported it into a blank database (which sometimes fixes bad indices). I'm
> > > glad
> > > there was a backup, though. That was good thinking on your friend's side.
> > >
> > > Regards,
> > > Bill Mosca,
> > > Founder, MS_Access_Professionals
> > > That'll do IT <http://thatlldoit.com/> http://thatlldoit.com
> > > MS Access MVP
> > >
> > > <https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-642707308
> > > 81E>
> > > https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-6427073088
> > > 1E
> > >
> > > My Nothing-to-do-with Access blog
> > >
> > > <http://wrmosca.wordpress.com> http://wrmosca.wordpress.com
> > >
> > > From: MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > [mailto:MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > <mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Ray
> > > Sent: Thursday, April 25, 2013 5:39 AM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > <mailto:MS_Access_Professionals%40yahoogroups.com>
> > > Subject: [MS_AccessPros] #deleted in a field value
> > >
> > > Can you shed some light on this mystery? A friend has an Access 2003 db and
> > > one
> > > table has some rows with #deleted in each field rather than the data that
> > > used
> > > to be there. I suspect that they have used the "delete record" button from
> > > the
> > > toolbar to delete a few rows (I know, not a good idea) and that something
> > > went
> > > wrong. When a query runs on this table it returns an error saying that a
> > > record
> > > has been deleted and then stops dead.
> > >
> > > We recovered the database from a backup and life has moved on. However, I've
> > > never seen this before, have you?
> > >
> > > Many thanks
> > > Ray
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>