[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Access 2007: Form problem, 'You can't save this record at this time'

Posted on 2011-04-26
Medium Priority
Last Modified: 2012-06-21
Good morning, I have been trying to make a database here with the help of some experts and have run into a dilly of a pickle. I'm attaching the form to this entry so that interested persons can look at the problem if I am unable to explain clearly enough.  The form controls of frmPtCharacteristics work fine until you attempt to add new data and then everything stops working.  Entries can't be created, I am unable to search between records with the combo box, and i get an error prompt when I move to the next form because it tries to close the original form and can not save it.
I have a form whose underlying table is related to several others in a one-to-many fashion with updated fields and join property 2 (include all records from 'one' table in many table).  
When I enter data the form associated with this table, and try to save a record I get the error 'You can't save this record at this time'.  I'm not sure what to do about this. The data entered IS saved, but then everything just seems to stop working.  Can someone please take a look at this, I'm stumped.

Thanks for the help,
Bevo S.

Question by:Bevos
  • 2
  • 2
LVL 24

Accepted Solution

Bitsqueezer earned 2000 total points
ID: 35470007

I strongly hope that this product was not invented with the help of experts...:-)

I would say, this "database" is a good example where you can find any problem which usually can be found in all kind of Access forums.

First thing is that it is based on macros. If you not plan to create a web database with Access 2010 you should immediately throw away all macros and start program with VBA. It's not really harder than this, but you can debug it - macros cannot be debugged (not in Access 2007).
I could solve your problem by converting the embedded macro as saved macro, after this little change it worked... but that doesn't mean the rest is OK.

You used multi-valued fields - they produce problems if you try to query them.
You used lookup fields on table level - they hide the underlying value if it would be an ID. But: You didn't use an ID although you have lookup tables (which is normally the right way) - all lookup tables should have an ID field as primary key (PK) - none of your lookup tables have a primary key or ID, you copy all the values to the main tables and produce a lot of redundant data. The database will be very slow in the end and has nothing to do with a relational database.
You can enter anything in the most fields - no validation. The search combobox is not refreshed after saving a record. The new record button has the same text as tooltip. Form objects have no meaningful name like "Command104", "Check180". Table and field names have spaces.

That are only the errors I saw with a quick view on some elements. I would say this "database" needs a complete redesign and a lot of learning about database design from you...



Author Comment

ID: 35470501
Thanks for the unsolicited critique.


Author Comment

ID: 35470542
In seriousness, I recognize these shortcomings already.  Changing the macros to VBA solved the error thought and I  begrudgingly offer you full points for your disparaging answer.
LVL 24

Expert Comment

ID: 35471349
Hi Bevo,

sorry, it was not meant to be disparaging - it was meant as accelerating incentive to you to not try to go on working on this way because you will get in trouble not at the current point but in future when you try to make more of this. It is very much easier to change the basics at the beginning and then go on developing, if you try to change these things in a further point of development you will have a lot more to do with it.
Unfortunately it is also the fault of Microsoft and Access that it simply allows to create such things and sell it as "features" (like multi-valued fields or lookup fields). It would be very much easier if they had implemented a multi-value frontend possibility with a normal lookup table for example or create a normal lookup table with a wizard instead of lookup fields on table level and so on.

Hope you feel not demotivated to go on developing databases.



Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

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

Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
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.
With Microsoft Access, learn how to specify relationships between tables and set various options on the relationship. Add the tables: Create the relationship: Decide if you’re going to set referential integrity: Decide if you want cascade upda…
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 …
Suggested Courses

834 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