You can ignore these posts.

These posts have no questions but contains what I call: "Sloppy MSAccess Snippets". They are little coding snippets or an application I've designed where I need to get some part of the code to use in another application. Some are little coding snippets, some are works-in-progress, and some are applications I've designed for some purpose.

** These examples are NOT documented and often contains commented out code which I've tried and found did not work.

They are not thoroughly qc'd to put in the MSAccess Code Bank but I wanted a place where I can go to download a piece of code I've done on a project to the computer I'm working on or share it with others (ie..izyrider).

I called this post "Sloppy Snippets" because that's what they are - sloppy. Plus I can quickly find this set of posts by the title to grab anything needed.

Feel free to upload any example code you might be working on in this set of threads without having to comment the code! All code examples are AS IS and are NOT necessarily guaranteed to be the best approach to use! There also is no assurance needed that any of the code will work! Nor is there any suggestion that the coding used is the best approach! Again, documentation, answering questions, critiquing the code, and explaining what the upload does is not the purpose of this set of threads. If you should download any of the examples in these posts, it should be understood that you have some coding experience to figure out what the code does without any comments or questions and that no guarantee is made that the code will work for you in your situation.

Several examples also have linked SQL Server tables in them (which I often work with.) This means that if you try to look at the data in the tables, you won't see it. The code also will not work until you convert the SQL Server tables to Access tables. You will need to open it using the Shift Key for the Access examples with SQL Server linked tables. The focus in these examples is not seeing the data in the table but grabbing some piece of code to do some purpose with again, the understanding that you can decipher what the code does and that you can determine if it's the best approach to use.

Lastly, attached to this post is a collection of dozens of word documents which I've zipped. Each worddoc show code to do a certain thing (ie...get last day of month, get first day of month, bypass autoexec, get age, etc...)

The attached is an example of a Bug/Fix tracking example.

The following is an example of a checklog tracking system.

The attached is an example of an emailing with Outlook program.

The attached is an example of an event scheduling/tracking program.

The attached is an example of an exporting routine.

The attached is an example of a logout script (ie.. it Grabs the loginID and it updates a status field to a sql server table connected to in the vbscript.)

The attached MSAccess file has a module in it which can be used to detect if the user tries to open the same Access file twice.

The attached example lets you schedule appointments in Access where you can write that schedule item directly into Outlook.

The attached is a check-generating example. It queries off of a measure type system and it will take the stored $ and convert it to a "check" written format.

The attached is an example of a progress bar.

The attached is a training example.

The attached is an example of tracking who's in and who's out in a company. Users can quickly mark if they are in or out and it can easily be viewed by others.

The attached is an example of a room scheduling/reservation program.

The attached is an example of a call log tracking and sending information/brochures program.