My database started giving me an error when it starts. Linkmasterfields property setting has produced this error: 'Return without GoSub'. I already checked the Link Master Field and the Link Child Field. They look right. I'm attaching a copy of my db. Thanks for the help.
Help with form error
- Thread starter nchickens
- Start date
Have you checked the datasource of the Link Fields.
Sounds like some where, back down the line, you have a problem with some code.
A simple field in a Form could require 10 or more queries and sets of code anyone of which can have an error.
Sounds like some where, back down the line, you have a problem with some code.
A simple field in a Form could require 10 or more queries and sets of code anyone of which can have an error.
boblarson
Smeghead
- Local time
- Today, 11:54
- Joined
- Jan 12, 2001
- Messages
- 32,040
A couple of quick things -
1. You don't need, and should not put
DoCmd.Save
in the form's before update event. For one, that has to do with DESIGN CHANGES of the form or report when that is in there. Second, if the Before Update event is firing, then you just need to let it go and it will be saving the record. The only intervention needed is when you need it to CANCEL and NOT Update. Then you need to put in
Cancel = True
Me.Undo
(you need to use the Cancel = True to tell it to stop the update).
2. Your software form I don't have time to run down all of it as I have to go catch a bus, but you should not be storing User Name in the record again; just their ID's.
3. You should NOT have a table for each software product. Your database is non-normalized and needs to have the table structure fixed before going on to anything else.
1. You don't need, and should not put
DoCmd.Save
in the form's before update event. For one, that has to do with DESIGN CHANGES of the form or report when that is in there. Second, if the Before Update event is firing, then you just need to let it go and it will be saving the record. The only intervention needed is when you need it to CANCEL and NOT Update. Then you need to put in
Cancel = True
Me.Undo
(you need to use the Cancel = True to tell it to stop the update).
2. Your software form I don't have time to run down all of it as I have to go catch a bus, but you should not be storing User Name in the record again; just their ID's.
3. You should NOT have a table for each software product. Your database is non-normalized and needs to have the table structure fixed before going on to anything else.
boblarson
Smeghead
- Local time
- Today, 11:54
- Joined
- Jan 12, 2001
- Messages
- 32,040
That took care of the error but you really need to fix everything I mentioned or you are going to have more serious problems down the line, including pulling data.
I would like to be able to normalize the database. However I'm not very good with databases and organizing them and I couldn't figure out how to organize a database that way. The reason I had a table for each software was because not all software needed the same fields. The reason each each table has User Name field is because that is the primary key and how each table is connected with a relationship. All the software is bound to the users except for microsoft office when it is a oem license. Thank you for any suggestions.
Similar threads
