Bevos
asked on
Access 2007: Form problem, 'You can't save this record at this time'
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.
EE-ABS.accdb
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.
EE-ABS.accdb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
Cheers,
Christian
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.
Cheers,
Christian
ASKER
Jeers,
Bevo