Replies

Hmmmmm ………..

I’m “reading between lines” …….

What is being asked is how to store a calculated result in a table. This should not be done ….. it should be calculated “on demand” dynamically when the result is needed. If the stored date entry should change for any reason …… the stored calculated result will not be correct. By calculating the result dynamically is the only way you can be completely sure that the result is correct at the time of execution.

The basic “rule of thumb” is: Do not store a value in a table that is “dependent” on another field in a table.
There are certain “special occasions” where it considered “allowable” to break this rule. But this is not one of those cases.

Sure …. the DateAdd() function is the correct way to calculate the result. But it result should not be stored in a table.

HTH
RDH

Usually when you start receiving an error in MsysObjects it indicates a database that is either corrupted or on the brink of corruption. You can attempt to repair the database but this usually does not fix the problem. If you have a recent backup, you may want to revert to it. You can try to import all the object to a new empty database. You may can recover that way.

Good Luck,
RDH

What Jack has replied will work as long as you use one of the allowable specified Zoom levels.

If you want to set the Zoom level to a custom percentage then you can use the following function:

‘ This function allows Report Custom Zoom level from 0% to 2500%
Function PreviewAndZoomReport(ReportName As String, ZoomCoeff As Integer)
On Error GoTo Err_PreviewAndZoomReport

If Not (ZoomCoeff >= 0 And ZoomCoeff <= 2500) Then

Sounds like you have a “Join” problem in the record source query.
You also say “form” and “print review” ….. you should be using a report. Forms are not designed to be printed.

HTH
RDH

Here is some code that I had “stashed” in my folder of things I might need one day. I have not actually tested it but maybe you can adapt it to your use.

Option Compare Database
Option Explicit

Const R_UPPER_TRAY = 1
Const R_LOWER_TRAY = 2

Type R_DevModeStr

The company I work for uses Dell computers exclusively. These machines have the installation files on them as Leif has replied. One other thing to look for is in the Root Directory …. see if there is a file named zztop.bat. This batch file, if executed will completely restore the computer back to the day it was purchased.

Good Luck,
RDH

If I remember correctly there is a limit of 255 files that can be place in a Root Directory. I remember a few years back that I was copying a a bunch of files from a CD to the harddrive and mistakenly copied them to the Root Directory (C:) and ran headlong into the problem you have described.

HTH
RDH

Maybe it was a mistake on my part to get involved in this thread. I have just tested the function again and can not find where it errors. The only thing I see is that I have Tuesday being calculated as “TU” instead of “T”. I thought that it may keep someone from confusing “T” with Thursday. As far as the “integers” … I have no problem knowing that the WeekDay() function returns an integer from 1 to 7. I have been programming in Access for almost 8 years and have seen Access get “sideways” by many things that can drive you completely nuts. I have only been a member here at this site for a short time but that does not mean I’m “New” at Access. I am a Moderator/Editor at A3 Forums (Access All Areas) and have answered many thousands of questions about Access at many sites. This is not to say that I can not be wrong (I have been wrong many times). I am very sorry if I offended you with my reply and will not respond further to this thread.

RDH

Well I guess it’s all personal preference …. but I would never declare a variable name of a Date/Time datatype “d”. I have seen Access confused by much less of my years of programming.

Anyway …. here is another function I quickly wrote that will do the same thing as yours without all the lines:

Public Function fDayAbbrev(dtEntry As Date) As String
Select Case WeekDay(dtEntry)

I have tested the expression on my machine. I have Access 97, 2000, and 2002 installed and it works in all versions. Only problem I can see is that you are using a “constant” as a variable name. “d” is a constant for “Day” in Access and could very well be confusing Access into producing the error message you are receiving.

RDH

Question 1: You will have to purchase the Developer’s Edition to get the Runtime ablity. You used to be able to purchase the Develper Tools Add-On but that is no longer available seperately. The Developers Edition will incude the whole suite. You have no other choice. You could choose to install Access only ……..

Question 2: According to Microsoft, you can legally install Office on your DeskTop and a Laptop …. if the Laptop is for your exclusive use.

Question 3: As long as you set Access 2002 to save as 2000 format, you should not have any problems working with files form either version. Unless you use a feature that is exclusive to Access 2002.

HTH
RDH

Also one of the main reason to split the db is that you can easily make chages to the Frontend db and simply overwrite the user’s Frontend to update it without effecting to data stored in the Backend.

RDH

First you should not use “system.mdw” as your “secured” security file. You should make a copy of it, rename it to something different, then use it instead. “System.mdw” should remain unchanged.

Your problem is caused by Access 97 placing “system.mdw” at one location and Access 2000 places it at another. So you now should have two copies. Access 97 is using one and Access 2000 is using the other.

You can verify this by searching you drive for “system.mdw”

HTH
RDH

If this is User Level Security and this is indeed your database, email me a copy of your security file (.mdw) that you have set up. I will email you back all the User Group and User Password information.

Remember ….. “it is illegal to break into a secured database without the permission of the owner”.

rdhicks@mindspring.com

RDH

You can ser the database to open “Exclusive”. This will lock everyone out until the database has been closed by the user. You should be able to find info on this in Access Help by searching for “exclusive”.

HTH
RDH