Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


The setting you entered isn't valid for this property

Posted on 2005-03-15
Medium Priority
Last Modified: 2008-01-09
the users have had my new access system for about 2 weeks and have asked for small changes every day.

Typically, I will open the specific form and navigate to the subform for the account that best demonstrates their problem.

I will then switch to design mode, make some changes, and switch back to form view.  If it looks good, I close the form and respond "yes" to the "save changes?" message.

Sometimes I get one or two messages that says
   "The setting you entered isn't valid for this property."

I can't figure out what property Access doesn't like.
I respond OK and everything seems to be fine.  

This has happened a half dozen times, but I can't get it to repeat, even when I try to do the same things immediatly afterwards.  
Any ideas as to what is going on?

Question by:rberke
  • 3
  • 2
LVL 85
ID: 13550639
Not sure what you mean by "navigate to the subform for the account that best demonstrates the problem" ...

Generally when you begin to get odd errors that you cannot recreate, you should import all your objects to a new, blank database and then ship this to your users. YOu may be experiencing database corruption. Before doing this, of course, make a copy of your database, and don't forget to import any toolbars if used. Have you tried to Compile your application? Are you shipping a .mde file to your users? I'm assuming your database is split into a frontend/backend and all users have their own copy of the frontend, all connected to the same backend.

Author Comment

ID: 13552385
My "navigate to the subform" comment really just means "I repeat what the user didn't like, then I fix it".
Also, the form that gets the error has a subform on it.

Yes, I have split database into
\\myserver\access\frontend.mdb    and also \backend.mdb

6 cpus on the Lan which all share frontend.mdb.   Since I am changing things daily, it is important that everybody get the same copy until things get a lot more stable.  

I suspect corruption might be the problem.  
When you say import all your objects do you mean running file>get external data>import and then going through
 all of these tabs one by one?   Queries     Forms      Reports     Pages      Macros     Modules,  then reattaching to the back end?

By the way, I can't seem to find the access commands for compiling an application. Compiling a vba program doesn't seem to do it.

LVL 85

Accepted Solution

Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
ID: 13553907
RE: Import ... yes, this is basically what you would do. Build a new. blank database and then click File - Get External Data - Import, then select all your tables, forms, etc etc. The linked tables will also be imported, so you don't need to relink.

Regardless of your development state, users should all have their own copy of the frontend. It's a simple matter to deploy 6 frontends, and corruption is almost assured with users sharing the frontend.

I misspoke regarding "compile your application". Should have read "compile your code", which you apparently are doing. In any event, to do this you'd open the VB Edit window and click Debug - Compile. If your vba won't compile, then fix any errors and try again.

Author Comment

ID: 13559624
"corruption is almost assured with users sharing the frontend"

Geez, I hope things aren't that bad. But, knowing how unstable Access can be, you are probably right.

I guess I should throw a copy command into the user's logon script.  

I'll run this for a while and see if the problems go away.

If nothing goes wrong in the next few days, I'll close this problem

Author Comment

ID: 13566129
Throwing a "copy command" in wasn't as easy as I thought it would  be.

All the "master" front ends are named "XYZ Front ddddd" on the server in a directory named XYZ program files.
Each also has a short cut name RunXYZ.

I finally came up with the following macro which copies these front end and installs the shortcut to the all users desktop.

md "c:\program files\XYZ Front Ends"
del "c:\program files\XYZ Front Ends\Front end*.mdb"
del "%ALLUSERSPROFILE%\desktop\RunXYZ*.tmp.lnk"
copy "S:\XYZ program files\Front End*.*" "c:\program files\XYZ Front Ends\Front End*.*"
copy "s:\XYZ program files\RunXYZ*.tmp.lnk" "%ALLUSERSPROFILE%\desktop\RunXYZ*.*"

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windows Explorer lets you open cabinet (cab) files like any other folder. In VBA you can easily handle normal files and folders, but opening and indeed creating cabinet files takes a lot more - and that's you'll find here.
When we develop an application in Ms Access 2016 we should also try to protect the queries, macros and table links. I know I may not have a permanent solution but for novice users, they will not manage to break your application. Below is the detail …
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
The Relationships Diagram is a good way to get an overall view of what a database is keeping track of. It is also where relationships are defined. A relationship specifies how two tables connect to each other. As you build tables in Microsoft Ac…
Suggested Courses

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question