Request: Need DB to store bugs

[Guus2005]

Hi,

I need a sample database to store issues/bugs/wishes on programs.
I thought this was a sample database in the latest Access version. But i'm on Access 2013 at the moment. Can you point me to a sample database?

Thanks!

Regards,
Guus

 

[mike60smart]

Hi Guus

The attached is the Issues Database Template from Access 2016.

View attachment Issues.zip

 

[pbaldy]

I have 2010 on this computer and searching on "bug" in the templates area finds a bug tracking template at office.com

 

[AccessBlaster]

Here ya go,

 

[Guus2005]

Thank you all for your input!

 

[isladogs]

Related to bug tracking, you may find this useful Access error codes

 

[isladogs]

I posted something very similar in this thread some time ago:
https://www.access-programmers.co.uk/forums/showthread.php?t=299991

Thought I'd compare both methods using Access 2010
Both are as you'd expect almost identical

Pat's code omits 6 common errors

ErrNumber	ErrDescription
3	Return without GoSub
20	Resume without error
35	Sub or Function not defined
91	Object variable or With block variable not set
92	For loop not initialized
94	Invalid use of Null

My code deliberately excludes these values which are in Pat's version:

ErrorCode	ErrorString
3004	**********
3072	|
3193	(unknown)
3194	(unknown)
3209	**********
3316	|
3369	**********
3392	**********
3395	**********
3416	|
3939	|1
4000	|
8057	|
31665	|
31671	|
32619	0,0

 

[isladogs]

The first link I posted was a static errors list. I posted the second link to deal with the fact that it changes between versions.

It seems those 6 'missing errors' are generic to VBA whereas the others are Access specific. They were also missing in the initial version of my list which was written by Hans Vogelaar. I modified his code to deal with them.
See this discussion https://social.msdn.microsoft.com/Forums/office/en-US/9683d44a-5ac3-45de-a654-5d4fd961203a/get-complete-list-of-access-error-codes-and-descriptions?forum=accessdev

As for the 'unwanted' codes like '**************' or '|', I can only assume they were assigned as markers related to a feature that wasn't implemented or later removed