This is a site dedicated to fellow developers seeking guidance in their problems.
If you came here by clicking the link on the company-website then please note that this sub-domain is geared at developers rather than anybody else (click here to return to the company-website).
As you will notice right away, this is just another construction-area, and as long as time flies, it will most probably continue to be one.
Until then, please dig through the little bits and bites I'm offering here.
If you're here once again - I have made a small change to the design in order to supply more than one Access-version at a time. I may continue to upload multiple versions sometime, allowing A97-users to make use of these archives as well (email me if you need i.e. an A97-version which is not offered here yet). If no AXP- or A2003-functionality is part of a sample, I'll supply A2000 only.
I'm always happy to receive feedback on the stuff supplied here - just drop me a line.
If you'd like to be informed when new stuff or fixes are made available, send me an email and you'll get notified.
|Filename||(Access-) Version||Size||last update||Description|
|Office Constants||289kb||30/04/2006||If you have to do Office-automation in larger corporations, there'll probably be more than one Office-version. As a consequence, you won't be able to use early binding in order to support all (compatible) Office-versions being used. Hence, you'll neither be able to use the constants provided by the respective application. The work-around is to provide these constants yourself.
This demo contains modules for the most commonly targetted Office-applications.
|Enhancing the focus||25kb||13/08/2005||This sample database includes a ready-to-use module that may help in the user seeing right away what control on your forms currently has the focus.
Being called directly from a control's event (OnEnter/OnGotFocus resp. OnExit/OnLostFocus) using its property sheet, either its backcolor may be set or a colored rectangle may be drawn around it (i.e. if its backcolor may not be set).
|Using a Treeview-Switchboard||57kb||10/08/2005||This sample database implements a switchboard-solution that uses a treeview-control that itself will allow the user to navigate to your application's objects by means of a hierarchical list.
The switchboard itself also includes a subform that may host other forms that are being shown after the user clicks a node in the treeview.
The hierarchy is being created using a simple and straight-forward table where you name the nodes, set the nodes' hierarchy-level and their order of appearance; This table will also be the place where you will state what form, report or function is to be called after the user clicks a node.
You will need the treeview-control installed on your machine. If you do not have the control, you will most probably not have the required license (included with i.e. VB6) to distribute it either. However, here's a setup that will install the treeview - so that you may at least try it out. This archive also includes the setup-script that is being used to install the control (InnoSetup-script).
This is the first version of the control - I will create a "wizard" for the control as well in order to allow the person setting up resp. changing the switchboard's contents by means of a form in the near future.
|Querying external DBs
"on the fly"
|47kb||08/02/2005||This sample database shows how to query an external database "on the fly", that is, without linking any table of that external database to the current one. Instead, a SQL-string will be constructed that may be used from within code or that may be passed to i.e. a combobox or listbox.
The MDB allows you to choose a database-file and will then display all tables and/or queries therein. After choosing a table or query, all records (if possible) will be pushed into a listbox.
This approach is most useful i.e. in scenarios where multiple backend-databases are being used. In such cases, using queries as tables and simply modifying those queries' SQL-portion after the backend-database has to be changed will be way faster than using linked tables along with TableDef.RefreshLink.
|Tab-Extender||34/31kb||18/12/2004||Introduces a small class that, with just a few lines of code, allows for the TAB-key to move focus between controls on different sections or containers.|
|Adjustable Listbox-Columns||A97||29kb||01/01/2002||This sample shows how to automatically resize a listbox's column-widths and, while at it, adjust command-buttons (that were created in order to serve as column-headers) as well. The command-buttons implement an ORDER BY-functionality which will re-sort the listbox's contents at the matter of a mouse-click and a single line of code.|
|DAO Lookup for listboxes||69/50kb||28/01/2002||A class that will find the first corresponding entry in (i.e.) a listbox whenever a key is tapped in. Encapsulated in a class to speed up process and to ease up usage.|
|mouse-pos relative to Access-window||41/24kb||01/01/2002||Sample-DB to retrieve the current coordinates of the mouse-pointer, related to the Access-window's position (helpful i.e. with self-defined tooltips).|
|Please hold on ...||>= A2000||25kb||01/01/2002||Easy to use class to bring up a form displaying something like "Please hold on a moment..." plus a status-message.
All that's needed is to instantiate the class and call the class' method to send a message - especially useful where a progressbar doesn't make sense or may not be used.
|ProgressBar Demo||A97||64kb||21/01/2002||Shows how to setup a (smooth!) progressbar without any OCX or even API - simply by integrating a prepared subform and a couple of lines of code.
Just insert this sample's subform into your own form and you're ready to go.
This sample A97-mdb includes full source-code and a demo showing the use with two concurrent bars.
|Selfdefined Inputbox Demo||A97||30kb||05/01/2002||Shows how to easily setup your own input-form to query a user's input instead of using the built-in inputbox [~shudder~].
All you'll need is one line of code in order to receive input from a user.
|Form returns values; Avoiding the mouse-wheel||>= A2000||118kb||29/01/2002||Introduces a module that enables you to receive multiple return-values from a form (works as wrapper for all calls to DoCmd.OpenForm ...).
In addition to the above this sample shows you how to avoid the nasty effects arising from unpredictable usage of a mouse-wheel - without using any API-calls or additional DLLs.
|Have a continous form resize itself to the amount of records||39/28kb||25/01/2002||Introduces a way for smaller tables resp. amounts of queried data to be shown all together in a continuous form.
The form will adjust its height to show all records while removing the scrollbar - thus avoiding the display-'bug' (or just strange behaviour by design?) in conjunction with continuous forms.
|Resize Hook||>= A2000||42kb||30/01/2002||If you'd like to prevent a form or the access-window from being resized below a certain level, the resize-event might be what you're using. However, I bet you're encountering a lot of flickering when doing so, right? Well, the flickering is caused due to the fact that - when this event triggers - the resize-action will already have taken place - leaving you one step behind events ...
Using subclassing, this sample database hooks into the windows-messaging-system which will be fired before the new size is passed to the form's resize-event.
Also in this sample: a small module which will help retrieve twips-per-pixel ratios.
|Setting your app's icon||
|19/02/2003||Access comes with the ability to set your own icon using the screen supplied under Tools/Startup.
Too bad an absolute path is required for this property called 'AppIcon', as just about always your users will install your application into a non-predictable directory, rendering your icon useless.
However, here's a sample with which you may - using just a couple of lines of code - set this property when your app's starting up.
In addition to that - if you use Access with V10 or higher (10 = Access XP) along with the Access XP file-format, this icon may be used for forms and reports as well.
|09/08/2004||Reading an Access-lockfile (*.ldb) you may determine which users (with their computer-names) are connected to a given Access backend-database.
However, information obtained this way isn't really precise, as i.e. a user may have failed to log out correctly, leaving a trace in the .LDB.
Using an ADO-recordset in conjunction with a specific schema one can create a recordset which will retrieve more exact information.
This is a sample database which comes with a form you may incorporate into your own application and which will show a roster of users currently connected to a database-backend.
|[Back to english website]||[Back to german website]|
Copyright 2000-2011: IntuiDev IT-solutions. All rights reserved.
For the lawyers under us:
All stuff provided here is provided as is, without any guarantee whatsoever.
Under no circumstances may the author be held responsible for any kind of damage (to your computer, yourself or even your cat) caused directly or indirectly by any of these applications or extracts of them - use at your own risk.
Also, the samples provided here may include third-party software that you will need a license for in order to be allowed to deploy/distribute them. The author may not be held responsible for legal issues arising from usage beyond EULAs connected to such software.
Last updated on 27/01/2011