No error warnings

[mhifd009]

I have a situation that never occured in access 97 and Im really stuck as to where to find the solution, in the reports and forms I have set various variables, and control parameters via the coding area, I totally check that the form has to be completed, but as with some of the reports, if there is a problem, i.e. a control mentioned in the code that is not on the form, or if one of the controls is not activated my save button has no reaction at all and at times doesnt write the record at all. please help if u can - error checking is ticked fully in options. The save button simply checks the controls have been entered correctly and then closes, i open a new record to the table on current to the form.

[NeoPa]

Can you post the code you have in the relevant Event procs.
I'm not sure what this is - it may be code related - but it's possible it's not Access related at all (maybe a glitch elsewhere). Try to explain clearly the circumstances under which the problem occurs too as this could also help.

[mhifd009]

Thanks for your reply, at its simplist form i have a report that displays a field / control and in the code on format I check to see if the control is > 0, if not visible = false else visible = true, if I delete the control from the report design and try to run the report the screen simply flashes as if it tried to run but no response, as soon as i re-instate the control - all ok, im sure that 97 gave error messages if control did not exist.

[mhifd009]

Just trying to sus this, I have these lines in code of report

Me![stabelheight].visible = True
Me![stableheight] = me![stable] + 30

as you can see spelling on 1st line incorrect - this gave no warnings or error, this type of error could take me an age to find if I have a lot of code

Any clues please

[NeoPa]

Do you run 'Compile {project name}' from the Debug menu when you're ready to test your code?
This should be found in a compile.
Otherwise I don't know what your problem may be.

[mhifd009]

Yes, aplying comply action, I have also found that when I write a new record in a form and the table#1 im writing to has a relationship with another table (needs to be corresponding record value in table#2) then no error warning, just doesnt write the record.

I have tried just in table design and i get 'Cannot add or change a record because a related record is required in table#2'

[NeoPa]

It's a long shot, but try typing DoCmd.SetWarnin gs(True) in the immediate pane of the VBA window (Ctrl-G), then trying again to see if error message shows. If that doesn't change anything then I'm stumped.

[mhifd009]

I really appreciate your patience with this problem, ive tried what you have suggested - no good - but again thanks for your efforts, I have reinstalled 2003 just in case, converted file to 97 and error appeared, but don't want to go back to 97 cuz of this. If you get any future solutions to this problem i will be gratefull and again thanks for your input.

[mhifd009]

Thought I would let u know for future ref : opened new DB and inported all tables, queries, forms, reports and macros and error came back, must have been glich in current db, again thanks for your advise and support,

[NeoPa]

Thought I would let u know for future ref : opened new DB and imported all tables, queries, forms, reports and macros and error came back, must have been glich in current db, again thanks for your advise and support,

Did you mean the error came back or it's now solved?
Otherwise why assume glitch in the database... Just curious you understand.

[mhifd009]

Expected error messages warned me of problem , the original DB was giving me no clues of errors - it seemed that error checking wasnt working, all solved now, thanks for your feedback - gud to know there are people willing to help - great forum.

[NeoPa]

Thank you.
Always nice to get feedback - positive feedback is best :).
This does sound like the problem I was trying to fix in post #7 though.
Did that not work for you? I was hoping it would allow more info from Access.

[mhifd009]

#7 suggested typing DoCmd.SetWarnin gs(True) in the immediate pane of the VBA window, this didnt solve the fact that i didnt get any warning. just wondering if i spell a control name wrong in code ie i spell me![name] as me![namr] by mistake - should the compile find this, it doesnt when i try it but when i run the report then the wrongly spelled control is found (this was basically the type of problem i was experiencing) access was not warning me that i had typed a control wrong in the code.

[NeoPa]

Ahh.
Did you compile it (explicitly - Debug / Compile {project name}) or just try to run it after updating the code?

[mhifd009]

I did it expicitly, the way i solved the problem was to create db1 and simply import 1 table and 1 report (the report with a control spelling mistake) and then tried to run and in new db1 i got expected error whereas in old db nothing - do you get a compile error if you compile {project name} when you have typed a control in wrong - im just curious you see.