Search results

The goal here is to update the users' Front-End modules automatically, without requiring any action on their parts. The two ways I usually accomplish this is either by replication, or by physically overwriting their personal copies of the Front-End file. As far as I know, both methods are going...

Two years so far and still going strong. I'll tell you what: when the application finally does blow up, and all the armies of the apocalypse descend upon me, I'll be sure to let you know. If nothing else, it'll produce some valuable field data.

Perhaps that's the intention, but it's very easy to implement one-way replication. Here's my method. I have a Design Master stored on my personal server. I also have a "master" Replica stored on a shared group server. Finally, all of my users have their own personal Replicas stored on their...

I've started using database Replication to keep my users' Front Ends up to date at all times. In most cases, I've found that users don't even notice their modules have been updated unless I tell them.

A few years ago, I started introducing a "lockout" function in all my databases. I introduce a linked table that contains just a single record with a single checkbox. Every user module is set to check the contents of this table every time a user opens the database, and every 5 minutes after...

Very nice. Thanks for sharing this. I have no use for this right now, but it's definitely nice to have it in the toolbox.

First, make sure your heading labels are in the Group Header, not the Page or Report headers. Right click on the Group Header to bring up the Properties, and set the "Repeat Section" property to Yes.

You need to add some code to the On Open event of the form that holds that field. When that form is opened, it needs to look at the maximum value of the date stamp in the target table. If that date is more than a month old, it can add a new record via an Append Query.

First off, Access is going to have to be running for this to work. As far as I know, there's no way to schedule a report to run unless at least one copy of your database is running somewhere. Assuming that someone is going to have a copy of the database open on Monday morning, you could tie...

What I usually do in cases like this is create a table that holds just a single date field. This table contains all possible dates within the range you're generating calendars for. (In my case, this usually means a full calendar year, but in your case, it may be a touring season.) This table...

I think you may be right...

I think the work needs to be done in the underlying query, rather than the report. You need to count how many orders there are for each part, as well as determine which order is the earliest, and calculate the inventory field based on that data. Here's an example of how that might work. The...

Will the report open if you open the underlying query first? Sometimes reports will respond better if the underlying data has already been processed. If it still doesn't work, my favorite diagnostic tool is simply to start removing fields until I find the culprit. If there are a lot of fields...

A DSum function would do that. Set the Record Source of the text box to: =("[And]","CurrentClients") By the way, if your field really is named "And", you might want to consider changing it. That's a protected word.

Step 1 is to decide when you want this data to refresh. Do you want it to happen every time someone opens the database, for example, or should it only happen when a certain Form or Report is opened, or should it only happen when a user clicks on a specific button? Whatever the trigger, you'll...

I think you're overestimating the hassle involved. If you've got a defined name range for the data you want in your Excel sheet, we're talking about three or four lines of code. You either trigger it when the database opens, or put in a button that allows your user to refresh the data as needed...

That's absolutely correct. Linking to an Excel spreadsheet will definitely impact your ability to open and save changes. My preferred solution is to import the data I need into an Access table (usually using the TransferSpreadsheet method). Importing the data will not lock the source in the same...

First off, you shouldn't be storing the days off in the Employee list table. You need one table that contains just a list of employees, along with whatever information is needed to calculate how many days off they're entitled to, such as their Start Date and Rank. Then, you need a second table...

The VBA code would be something like: DoCmd.OutputTo acOutputReport, "YourReportName", acFormatRTF, , True

I started with the assumption that what you're attempting to do can't be done natively. Access has no internal function that I know of to facilitate mirrored printing, which is essentially what you're trying to do. Since I didn't think one report could do what you need, my idea was to split it...