Search results

That is definately another thing to try. I will scan the tables. Will let you know if I find something. Thanks.

Hi, Thanks a lot for your suggestion. I'm going to try it first thing tomorrow morning when I have access to the database again. Your suggestion appears to be quite hopeful I think, thanks!! By the way, it is definately in the after update event. But it is not bound to a field. Will keep...

By the way, I use access 2003. With following record locking properties: Default open mode is shared Default record lockig is no locks Open databases using record level locking Is that information of any use, do you need more information?

I already did that once. Only ending up with the same problem. Any other suggestions.

Hello everyone, Since lately I am having problems with a multi user database with front and back end. It is a IT Helpdesk tool. I get the follwoing error. Either when entering a new record or updating an existing record it freezes. I can navigate between existing records. After entering and...

Thanks for the advice. I tried it immediately. However, the problem stays there. So I add a new record and everythink works fine until you click in one of the subforms. It then jumps to an old record, always the same one. When you go back to the new record you can add data in the subform, but...

Hi, Since recently I have an issue when adding a new record. I have a main form with two subforms on it. When I enter the data in the main forms' fields everything is alright. When I want to enter data in any of the subforms, on entry it first skips to a different record. This is always the...

Currently using Access 2003. However, the database has been converted from Access 97 to 2003 a couple of years ago. Any ideas?

Hi Everybody, Been looking on the web to see if other people have similar problems. I think my issue can be classified under "the bookmark bug" (see: http://www.allenbrowne.com/bug-04.html) On both forms there are unbound listboxes by which you can navigate to the record using the following...

I have taken a closer look at it. You are viewing the record that you select. But when you then change a random field on the form it changes the data in that particular field in the preceding record. Very strange.

Hello everybody, Here's the story. We have a database which functions as CMDB and Helpdesk tool with two main forms, a helpdesk form which registers calls and a hardware form which contains details of all hardware items also with which users own it and from which department they are. This has...

I have tried to import everything into a new database. Deleted the indexes and moved the data via an appeend query into a new table. Still the issues remain that after a (short) while it starts writing in the preceding record. I will open a new topic about this as this issue is not directly...

I am now seriously doubting whether the issue stems from the code I use. In principle it all works, only for a short while. Is it possible that the indexing of the table is corrupt somewhere. Apparently the database did crash a while ago with the following error: The database .... needs to be...

I'll see what I can do a.s.a.p.

Ok, I am going to give that a try. Hmm, it does not appear to be working. This is quite an irritating issue. I'm not sure what the source of the problem is, is it the code or something else. Especially since it always starts messing about with the preceding record. What I have also tried...

The listbox is on the mainform. It gets the data from a query. The approach you mention is unknown to me, could you explain?

Ok, let's see. The story is the following. We have an existing helpdesk database with which the helpdesk registers calls. However, it has very limited search features. So my aim is to add some features such that active calls can be found with ease. To make the picture complete, here is some...

Ok, tomorrow when I have access to the database again, I will give you some more information on the code. I probably can't get a copy up here as I am not allowed to. Will see what I can do tomorrow a.s.a.p. Thanks already.

Hi, In principle this solution works. The IT employee is changed and the call disappears when set to solved. However, after a short while it starts malfunctioning. It does not want to close the call and closes the preceding call. It also does not want to change the IT employee, but changes it...

That seems to be a good solution. I am going to give this a try first thing Monday morning when I get my hands on the database again. I will let you know if this will cure the issues, I am hopeful it will. Really thanks a lot.