If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
All my forms Modified date are the same after compact and repair
I have an access front end that compacts and repairs after each time it
closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 |
#2
|
|||
|
|||
All my forms Modified date are the same after compact and repair
"Jerry8989" wrote in message
... I have an access front end that compacts and repairs after each time it closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 I don't think there is any patch for this behavior in Access 2000. I don't recall if it happens in Access 2002. It doesn't happen in Access 2003. I suppose you could, if necessary, write some code to read and store the last-modified dates before compacting, and then restore them afterward. -- Dirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup) |
#3
|
|||
|
|||
All my forms Modified date are the same after compact and repair
On Tue, 8 Jan 2008 13:45:03 -0800, Jerry8989
wrote: I have an access front end that compacts and repairs after each time it closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 Turn off Compact on Close, for starters. A frontend generally doesn't need to be compacted AT ALL since it (usually) doesn't contain any data. As for the modified date... it's a pretty much useless attribute. If you need to keep track of when the design of a form or report was modified, you'll need to do so yourself. I keep a table named Modifications in the frontend mdb file, and (manually) fill in the name of the object modified, the date and time (default value Now() ), and a note as to the nature of the modification. One point though: users should generally be using a .MDE file, not a .MDB, and should not be modifying the design themselves; so the whole question becomes moot. John W. Vinson [MVP] |
#4
|
|||
|
|||
All my forms Modified date are the same after compact and repa
Thank You for your reply.
I fully understand what you are saying but the situation i'm in doesn't allow me to do some of your suggestions. I can't turn compact on close because we have imports that indiviual users run locally where the data is stored on the front end. I can't do this on the back end because the table populates and deletes and if multiple people run the same import we would have a data issue. I have to keep it an MDB because we have macros running and MDE have issues with running our macros. Keep a table manually updated will not work for us. I use the modified data to make sure certain changes were made correctly. If Microsoft has known about it since 2004 why isn't there a fix? Thank you again for your replies "John W. Vinson" wrote: On Tue, 8 Jan 2008 13:45:03 -0800, Jerry8989 wrote: I have an access front end that compacts and repairs after each time it closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 Turn off Compact on Close, for starters. A frontend generally doesn't need to be compacted AT ALL since it (usually) doesn't contain any data. As for the modified date... it's a pretty much useless attribute. If you need to keep track of when the design of a form or report was modified, you'll need to do so yourself. I keep a table named Modifications in the frontend mdb file, and (manually) fill in the name of the object modified, the date and time (default value Now() ), and a note as to the nature of the modification. One point though: users should generally be using a .MDE file, not a .MDB, and should not be modifying the design themselves; so the whole question becomes moot. John W. Vinson [MVP] |
#5
|
|||
|
|||
All my forms Modified date are the same after compact and repa
Try doing your imports to a temporary database.
Tony Toews has an example at http://www.granite.ab.ca/access/temptables.htm In that way, you don't have to care what changes have been made to the front-end: you can simply replace it. (While you're at Tony's site, check out his free Auto FE utility at http://www.granite.ab.ca/access/autofe.htm) -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "Jerry8989" wrote in message ... I can't turn compact on close because we have imports that indiviual users run locally where the data is stored on the front end. I can't do this on the back end because the table populates and deletes and if multiple people run the same import we would have a data issue. I have to keep it an MDB because we have macros running and MDE have issues with running our macros. Keep a table manually updated will not work for us. I use the modified data to make sure certain changes were made correctly. If Microsoft has known about it since 2004 why isn't there a fix? Thank you again for your replies "John W. Vinson" wrote: On Tue, 8 Jan 2008 13:45:03 -0800, Jerry8989 wrote: I have an access front end that compacts and repairs after each time it closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 Turn off Compact on Close, for starters. A frontend generally doesn't need to be compacted AT ALL since it (usually) doesn't contain any data. As for the modified date... it's a pretty much useless attribute. If you need to keep track of when the design of a form or report was modified, you'll need to do so yourself. I keep a table named Modifications in the frontend mdb file, and (manually) fill in the name of the object modified, the date and time (default value Now() ), and a note as to the nature of the modification. One point though: users should generally be using a .MDE file, not a .MDB, and should not be modifying the design themselves; so the whole question becomes moot. John W. Vinson [MVP] |
#6
|
|||
|
|||
All my forms Modified date are the same after compact and repa
If Microsoft has known about it since 2004 why isn't there a fix?
There was. It was called Access 2002/XP, 2003, 2007. The article you specify refers to it as a "problem" with Access 2000. That does not mean that Microsoft considered it a "bug". In any case, the behaviour was changed in subsequent versions. -- HTH, George "Jerry8989" wrote in message ... Thank You for your reply. I fully understand what you are saying but the situation i'm in doesn't allow me to do some of your suggestions. I can't turn compact on close because we have imports that indiviual users run locally where the data is stored on the front end. I can't do this on the back end because the table populates and deletes and if multiple people run the same import we would have a data issue. I have to keep it an MDB because we have macros running and MDE have issues with running our macros. Keep a table manually updated will not work for us. I use the modified data to make sure certain changes were made correctly. If Microsoft has known about it since 2004 why isn't there a fix? Thank you again for your replies "John W. Vinson" wrote: On Tue, 8 Jan 2008 13:45:03 -0800, Jerry8989 wrote: I have an access front end that compacts and repairs after each time it closes. What it is doing is setting the modified date to all of the forms to the system time and date when the front end is closed. This is the link from Microsoft but it doesn't have any resolution. Does anyone know how to correct this? http://support.microsoft.com/kb/244642 Turn off Compact on Close, for starters. A frontend generally doesn't need to be compacted AT ALL since it (usually) doesn't contain any data. As for the modified date... it's a pretty much useless attribute. If you need to keep track of when the design of a form or report was modified, you'll need to do so yourself. I keep a table named Modifications in the frontend mdb file, and (manually) fill in the name of the object modified, the date and time (default value Now() ), and a note as to the nature of the modification. One point though: users should generally be using a .MDE file, not a .MDB, and should not be modifying the design themselves; so the whole question becomes moot. John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|