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
|
|||
|
|||
General Access DB Question
I have been working with a database (that I have created three times from
scratch) with many macros and vba modules. Every once in a while when opening the file it looks like all of the vba code gets deleted and when I fix it up the program always opens with the same following message: "The system you are saving to does not have enough memory to remove personal information from file properties. All personal information may not be removed" I have not been able to find any information regarding this message and I have to keep rebuilding the database, after the second time I had exported all of my vba code but this is getting ridiculous. Does anyone have any ideas why this might be happening? Any help would be appreciated. |
#2
|
|||
|
|||
General Access DB Question
I have had no experience with the same or similar message with any version
of Access. However, for anyone to suggest a solution to what would appear to be a bug, you should really post both the version of Access / MS Office and the version of Windows you are using. Larry Linson Microsoft Office Access MVP "redD" wrote in message ... I have been working with a database (that I have created three times from scratch) with many macros and vba modules. Every once in a while when opening the file it looks like all of the vba code gets deleted and when I fix it up the program always opens with the same following message: "The system you are saving to does not have enough memory to remove personal information from file properties. All personal information may not be removed" I have not been able to find any information regarding this message and I have to keep rebuilding the database, after the second time I had exported all of my vba code but this is getting ridiculous. Does anyone have any ideas why this might be happening? Any help would be appreciated. __________ Information from ESET Smart Security, version of virus signature database 4050 (20090503) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 4050 (20090503) __________ The message was checked by ESET Smart Security. http://www.eset.com |
#3
|
|||
|
|||
General Access DB Question
recommend you split your database, all tables to a Backend file, and all
other objects to a Frontend file, and back up both - the backend db each day (or each time you edit data), and the frontend db each time you make design changes. until you can identify the problem and prevent it from recurring, at least you shouldn't have to keep building the db from scratch. hth "redD" wrote in message ... I have been working with a database (that I have created three times from scratch) with many macros and vba modules. Every once in a while when opening the file it looks like all of the vba code gets deleted and when I fix it up the program always opens with the same following message: "The system you are saving to does not have enough memory to remove personal information from file properties. All personal information may not be removed" I have not been able to find any information regarding this message and I have to keep rebuilding the database, after the second time I had exported all of my vba code but this is getting ridiculous. Does anyone have any ideas why this might be happening? Any help would be appreciated. |
#4
|
|||
|
|||
General Access DB Question
One idea to narrow it down.....can you see (e.g. from header, footer, title
bar of the error message block etc.) which "software" is generating the error message? E.G. from the VBA/code/custom application written in Access, from Access/Office or from Windows? This message sounds so specialized that my first guess is that it's an error message in the VBA/code/customapplication. If so you might track it down there. |
Thread Tools | |
Display Modes | |
|
|