Here's a little app I wrote a couple of years ago. Even though I hesitate to upload full applications, this one is a full application (minus comments in the code). Use and modify it as you wish. I hope some find it useful. It's not the best coding but it does work. (I could've done a much better job on the coding for this one.)

It could be refined a tad more but I think you'll find it has pretty much everything you'll need. It was originally designed for SQL Server tables but I converted them to MSAccess tables. The other developers really liked using it.

The program works best on a 1024x768 screen but it will fit on an 800x600 (mostly due to the ability to copy and paste error screen snapshots into the forms which also saves the picture in the table.)

The developers also wanted a choice between 2 different style Main Menu's so it has a rather nice feature where you can select which type of Main Menu you like. Besides that, it has lots of good stuff including the ability to make steps on the solution, assigning tasks, severity levels, re-creation steps, quick-keys, reporting, and an in-depth search routine as well as filtering on unsolved issues or for "my assigned" issues (etc...etc...)

Let me know if anyone finds it helpful. Use this to get ideas on creating your own bug tracking program (or use this as is - there's no royality (and no updates planned) - it's totally free though).

Designed and deployed using Access 2000.

I made it to track daily activities and incidents when I worked security at a 4-star hotel.

There is a main switchboard where you select options ranging from beginning a daily activity log, work on your log, begin or edit incident reports (which can hold photographs).

See the readme for a few hints.

Attached is one (of many other) examples on how to create a simple pop-up search form. There are multiple, multiple different ways to do a search form but I thought I'd post this simple example if someone is looking for ideas.

(Again, this is very basic).

Here's an example of a cardfile program I created. Has a nifty little alphabetical search. Sorry it's not commented very well (I'll work on it.)

It will add your user login name automatically to the dbo_THC_AdminTable permission table when you first use it (note: new users given admin permissions.)

Hold the shift key when opening to get to the code.

Add card names and websites (with ability to double-click and go to website.)

Also has color scheme demonstrating the ability to configure your only color shading (ie. blend a yellow color to a green color - looks nice.) (click Change Colors button below Exit button on Main form.)

I will have a new version soon.

Here are two samples of ActiveX tree view for those who are looking for it.
Thanks to "hammbaka" and "huela" who posted em and I found em in Old Posts.
Many thanks also to Marvels who shared another code but I couldn't get it to work as I couldn't reconstruct its query, he may complete his sample and put it here for use.

The attached application is made up of 4 forms which can be imported into any access database and should work without any further set up required.

This application is intended to allow your users to create their own simple queries in a safe and controlled environment. You should never give your users direct access to your data, so this is intended as a barrier between the users and your precious data!

I appreciate there are a number of improvements to be made, this was simply constructed as a proof of concept and after a recent thread I have decided to share what I have got so far.

To use the application, simply run the sqlbuild form and it picks up the tables in your database, along with their respective fields, etc. The rest should hopefully be pretty easy to work out!

If you come across any bugs, problems, have any questions, comments or criticism - please feel free to contact me via these forums!

Please note that this application is still in development and as such bugs will occur!

Finally, enjoy!

-George

This is a Survey Tracking program with many options. You can change the title (Low Income) and other stuff in it without affecting how it works. It allows you to configure how you want the answers (i.e. A, B, C, or integer value, or string value).

I need to revise it a bit but I thought I'd post it as is for now - It may not be fully working. I should have a new, more flexible revision sometime soon with comments.

I was going to upload this example to the previous post I made in this forum on getting the user's window loginID but since I made quite a few changes and enhanced that example, I thought I'd make this a new post. This is the GetUser example which retrieves the windows user loginID to an MSAccess form (or anywhere in an mdb). Here's a list of what this new example does:

1. Simply call the GetUser function to retrieve the windows loginID of the current user using the computer. This example has a very nice Main Menu form which demonstrates how all this can be done. I also added some handy functions and if you look at the modules, you'll notice that the 'Check For Admin' module has the functions which do the security checks and the 'UserName (GetUser)' module is the function which retrieves the windows loginID. The 'FormInfo' and 'SystemInfo' class modules are from the Access Developer's book by Sybex and I import and use these modules in every mdb I develop (see comments in the modules for all the things you can do using them.) The FormInfo is used and called in the GetUser form's OnOpen event to manipulate the form without the form's caption bar. The SystemInfo class module is needed to utilize the GetUser function.

2. =GetUser() can be used anywhere (i.e. in a report, in a query as an expression, on any form, or in calling another function.) It is a very trusted method which I've used for many, many years now. You should have a field in your data table (called something like: EnteredBy) and then on the form, simply set the default value of the EnteredBy field to =Getuser(). Along with a DateEntered field, this is a great way to track who entered the record and when.

3. This example also shows how you can set up a permissions type system giving users different security levels. This is done via having a 2nd field in the dbo_AdminTable called SecurityLevel (integer field type). Additionally, another relational table could be added describing what the integer values represent. I prefer using this method versus making users always enter their username and password (and it will make your users much happier not having to do this.) I honestly don't know why developers like to make user's enter a username/password when this can so easily be embedded with a secure way to get the loginID.

4. I made this example so you can change and 'simulate' on the form with another user's loginID in the dbo_AdminTable. Notice when you change to another user's login, that buttons on the form become visible/invisible or enabled/disabled depending on their security level (which is called via the function: RetSecLevel in the Check for Admin module.) The loginID is passed to RetSecLevel and it returns the SecurityLevel value from the dbo_AdminTable.

5. I also demonstrate (via the IsAdmin function) how you can just determine if the user is in the dbo_AdminTable versus utilizing a SecurityLevel field. So what you could do is have a separate table as an "admin" type table and use that to determine security by simply checking to see if the loginID exists in the table. In a scenario, you might have an AdminAllowEdits table or an AdminReadOnly table and check for loginID's in those tables (but I prefer and encourage simply using a SecurityLevel type field.)

6. The example also shows how you can make buttons visible/invisible or enabled/disabled depending on the security level of the user in the dbo_AdminTable. When you change to another loginID, you'll notice how the buttons change on the form. In an application, you might show an "Admin Functions" type button if the user's securitylevel value is 5 for example. In this example I made it so the buttons change if the securitylevel is > 3. But try changing the loginID to "JoeSomebody" in this example to see what I mean (note: you'll have to click the "Change to Me" button or to another user with a higher securitylevel if you want to close the form.)

7. This example utilizes a "MainFormBackGround" which is a technique I've often used whereby you can 'disable' the MSAccess Menu items by maximizing the MainFormBackGround form and then making the Main Menu form a Popup/Modal. This is ideal versus making the menu items invisible which you then have to make visible again to do any designing. The MainFormBackGround hides access to the tables, forms, queries, reports, etc.. and the popup/modal form "locks" it so you can't close the MainFormBackground.

8. Hence, in this example, you cannot get behind the scenes unless you have a security level > 0 (so when you click the Close button, the form will close) or you must open the mdb while holding down the shift key.

9. When you first open the mdb, it will detect that your loginID is not in the dbo_AdminTable and it will automatically add your loginID (with a security level of 1 so you can utilize the Close button on the Main Menu form.) This is done via the IsNewUser function in the Check For Admin module and is called when the Main Menu form opens (although I probably should have put the call to the IsNewUser function in the OnOpen event of MainFormBackGround.) There's also a button on the Main Menu form to add new users or edit your loginID/Security Level. If you accidently change your loginID's security level to 0, you need to open the mdb with the shift key and edit the dbo_AdminTable (or change to a user with a higher security level.)

10. Use the techniques in this example to put into your application and make your life (and your user's life) much easier when it comes to getting the windows loginID and setting up permissions (also see the example I posted in the code bank on how to get Active Directory logins which also has a security level example.)

I made a 2000 and 2002 mdb version in the zip file. There's absolutely NO hidden secrets, hidden routines, or complicated coding involved or any trial type usage.

Please send me feedback if you find this example useful. You're free to use any part of the code.

Includes a version in 97, 2000, and XP.

Enjoy.

Here's a couple of more search examples (quickly done). Includes listboxes to show tables, queries, forms.

This Game is based on Old Microsoft Windows Mine Sweeper Game (If Remember).
In fact its a good example for those who looking for crating forms in realtime with code and assign code to events of controls.

To run the game first extract the files in a directory and run the "Mine Sweeper.mdb" file, the first menu ask you the number of rows and columns.

You can select any number between 3 and 10; also you can determine the total number of mines in the game; after that click START to begin the game.

By clicking the buttons they will be disappeared as well as the vicinity buttons if they are not Mines (Obviously you will loose the game if click a Mine).

Numbers on the buttons show the total number of Mines in vicinity of that button; you should decide as per these numbers to click safe buttons.

Right Click will mark up the button as a Mine; if you guess the button is a Mine simply Right Click on it to be marked as a Mine.( be careful it can be a wrong presumption)

You can Share it with other friends if you like.

Hope you enjoy it.

This is still a work in progress but I thought I'd upload what I've done so far. (requires Access 2000 or greater)

It basically plays Jeopardy (I'm still working on the double-part.) You can also edit the questions and make your own questions. You play against 2 computer opponents. You can adjust how fast the computer skill levels answer in the Change Default Options button on the Main Menu (and also set the probability of Computer Player 2 and 3 being correct.) I'm working on adjusting the code for this also but they are somewhat competitive so far.

Again, it's still a work in progress so if you get a few errors, know that I will be uploading a better version sometime.

Hopefully it's fun for you. Feedback on how well you like/dislike it is encouraged.

(sorry but I'm not supplying the source code on this one. Mainly because it's rather sloppy.)

Version 3 Now uploaded (08/07/2008):

Changed:
1. Better computer opponents (and you won't get the same 2 computer components for a specific game - new logic.)
2. Can change the probability more accurately that the computer will be correct and make it so it's very challenging against the computers (or very easy).
3. New logic re-written on the time they answer and more accurately reflecting with their default settings and their probability of being correct.
** 4. You can change the name on the main form from MSAccess Jeopardy to whatever name you want to call it (for example, if you wanted to enter questions for another topic such as Crafting, etc... you could call it Crafting Jeopardy and enter Crafting questions!)
** 5. You can now add Categories to a computer player in which that computer player will then have better odds of answering something they have listed in their categories (and a better chance of being correct - ie. the computer might also 2nd guess their answer if it's a category in their listing.)
6. You can adjust the TimerInterval to make the answer clock run faster or slower.
7. You can set the Answer time limit.
8. You can change/adjust the default settings in the middle of a game (ie. you can speed up or slow down the timerinterval or other computer probability default settings while playing a game instead of having to quit the game.)
9. A few other bugs fixed.

Sorry though, no Double-Jeopardy or Final Round yet - still working on it. I'm also working on when you "Buzz" in, you have a certain number of seconds to answer. As of now, you can take your time answering the question once you've buzzed in.

Attached is 2 cool menu forms in the attached zipped mdb you can utilize in your projects (these are done in Access 2000 but can be used in any Access version.) If you like them, maybe send me a PM letting me know you like them. I also included some background .gif files of different colored rectangles and shapes you can replace in the form.

To me, a good main menu form says a lot about the quality of the program so I hope you can find them beneficial.

Also notice how I've changed the pointer to a pointing hand (this is very easily done with a simple module.)

Key Point if you modify either menu -> make sure you bring the text box with the wording to the FRONT (ie. Bring to Front).

On the 2nd Menu, make the yellow color box (or whatever highlight color box you choose to import to the form), the 2nd to the front otherwise it will cover over the caption text and won't look like it's working (well...you know what I mean - Bring to Front or Send to Back.) The order of Front-to-Back makes a difference for the highlighting effect.

Again, I hope you like them.

To create a word document (ie. template - *.dot) linked to an mdb, there are a couple of different ways. I personally just open a Word Document and use the MailMerge option (Tools -> Letters and Mailings -> MailMerge wizard) to "link" to an MSAccess table (or query) and use the Word MailMerge toolbar to insert the data fields where I wanted them and then save as a *.dot. And then I have a button on the MSAccess form which just opens the Word template.

Here's an example of an mdb and a word dot. Opening the Word dot, left-click on the area above and show the "MailMerge" toolbar (or Click View -> Toolbars -> MailMerge). Click the <<abc>> to see the field names (which are surrounded by << and >> in the document). Use the "Insert Merge Fields" button (2nd to the left of the <<abc>> button (NOT the Insert Word Field but the next one to the left - make sure "Database Fields" is checked.) Click the <<abc>> to see the data and again, remember that, to navigate from record to record, you need to use the red < > buttons on the MailMerge toolbar. Edit as you need to and save as a *.doc. If you want to revise the *.dot, first save it as a different name, make your modifications, and then save it as the original name .dot (since you cannot save changes over a *.dot file.) You could do this all with a *.doc but I prefer to use a template (*.dot file) so users don't accidently make changes when viewing it and save them (they are forced to give it a different name) - so the *.dot is protected from accidental changes and is always the same when you pull it up the next time - actually though, you may need to make the *.dot read-only (unless again, you rename it, make the changes and then save it to the original *.dot name - or just delete and create a new *.dot file from scratch.) But if you want to make changes on the fly even when viewing the data in the document, simply make it a *.doc versus a *.dot file and open the *.doc file in the button code.

See attached example. IMPORTANT: You MUST put both the mdb and both *.dot files in a folder called c:\HelpForOthers (otherwise in Word, you'll need to re-do the connection to the mdb data source (ie. 2nd button from left on the MailMerge toolbar - ie. "Open Data Source" and navigate and change to the new mdb location and select the table/query) and also change the code behind the buttons to open the *.dots in whatever folder you put them in.) Also note, you cannot link to a query with criteria in it (hence the make table routine to make the: CurrentWordRecord table and open the current record in Word in the "Open Word Document On Current Record" button.) If you're doing this all with your mdb and document, simply use the MailMerge wizard as it walks you through the 3-4 steps to connect to your mdb table/query. Then use the code in the example mdb supplied to open your document.

Note: You can also just open the WordMailMergeToCustomerMDB.dot without opening MSAccess.

Last Note: You need to close the *.dot files before you can make changes to the mdb (since a connection is established when the *.dot's are open).

I also like the code supplied by JManSF so I've also attached the code he has written in a pdf (WordExport example.pdf) and posted (I hope he doesn't mind). This shows how you can programmatically code the fields into the Word Document via MSAccess. See notes in the pdf for instructions and code example.

Attached is a set of some good icons (*.ico files) to utilize in an MSAccess form.

The following attachment shows an example of entering orders for a customer and how to do some locking of customer/order data fields depending on if an order for a customer has been marked paid or not.

Notice that to delete a customer, the relationship is set up so that you must first delete their orders. If an order has been paid, you cannot delete that order (and hence, not delete the customer.)

Also shows total paid/due for each customer.

I did this example very quickly (i.e. within a couple of hours) so I apologize if there are any errors.

V2: - fixed problem with it not updating the DateModified and ModifiedBy fields for a customer.
V2: - Can now print totals report and Customer reports.