Question MS Access: Issue Tracking Database

[scs3drg]

Hi, first post and not much of a techie so go easy on me.

I downloaded this template from the ms website and done some light modification to meet the requirements of what we're doing.

I need up to 20 users to use it concurrently to raise issues, however after initial testing it failed because it assigned two issues raised at the same time by separate users with the same id, one of which was lost.

Is there anyway I can get around this?

Thanks in advance

Rgds
Dave

 

[BobMcClellan]

there is no info about the "template" you are using but....
Aside from using record locking....
From what you've described, I would think you would have an "issues" table.
The foreign key for the table would be joined to whatever the issues are related to or even by userID. This way each user pumps in their own issues as opposed to overwriting an issue being edited by another user.. This would also lend to following an issue as users comment or participate in it's resolution. You could then in essence... "follow the thread".
hth,
..bob

 

[scs3drg]

Hi Bob

Thanks for taking the time to respond. The template I'm using in on the link below

office.microsoft.com/en-us/templates/issue-database-TC001218693.aspx?CTT=5&origin=HA001234159

Hopefully this helps understand the problem.

Regards

Dave

 

[gemma-the-husky]

there are a number of ways of alllocating IDs

now one often mentioned here is to take the highest number in a table, and add 1

but if two people try to add a record at the same time, they will get the same number - which may be the issue you have

so - an alternative is to issue the next number fgrom a central table, and increment it straight away

then user 1 gets number 2345
user 2 then gets 2346

now the problem is that is user 1 scraps his entry, you lose his number, so it depends how important it is that oyu maintain in intact sequence

hence, a refinement of this, is to get the number only at the stage you accept the order, but with this version, you dont get to see the number until right at the end.

-----
so you need to have a think about all this, to decide how you want to implement your number issues.

 

[scs3drg]

Gemma

It sounds like your on the money, id sequence integrity is not important to me, can you point me in the direction of where I could see an example of this implemented?

Dave

 

[richard bro-42]

I have experienced this exact same scenario. I solved by creating a "KEY WORD" tbl. where I force a discrepancy entry to use specific words for registering their issues. Then My programmer put a small amount of code in that sets in action a word match with any other items "objects" already entered. If there is a match then a message box displays a message,"there is already a discrepancy enter that matches this one for this same item, Do you want to enter anyway? you then have a choice Yes or No.
You may have to get help with the search code.