Rowsource 2000

[Former]

I'm using Access 2000.

I open a form in design mode and place a combo (or list) box on the form, the wizard appears and I go through the necessary steps to display what I want.

I then view the form and it's perfect.

I then close the form saving my changes thinking what a wonderful job I have done.

Howeever, when I return to my form the rowsource of the combo has completely changed.

Is this a reported problem ?

I have put in a bodge to get around the problem by setting the rowsource using code on the Load event of the form, but I would obviously rather the thing worked properly.

For your information.

Rowsource before :-
SELECT tbl.id, tbl.name FROM tbl

Rowsource after :-
SELECT tbl.id, tbl.id FROM tbl

Thanks to anyone would reads through all of this, let alone replies.

 

[ElsVanMiert]

Sorry, but Access will definitely not change the rowsource on its own. I suppose that there is a "forgotten" function in one of the form's events that modifies the rowsource.

 

[TGHockett]

Former... I agree with Els, and just today I created combobox for the user to select which record they wanted to edit, and the row source was set by the wizard to be the name of the event procedure used for the combobox record selection process.

TGH

 

[Former]

Would it be possible to send either of you a copy of the database.
My sanity is at stack.
Thanks in Advance
Former

 

[ElsVanMiert]

What do you mean by "copy of a database"?

I think that you just should analyse your form in design view for the existing events. I think that deleting the load-event will repair the situation.
If you should not find the solution, then you should create a new MDB, import all objects (besides the "magic" form) and re-create this form from scratch. But I do not believe in magic.
Good luck and keep us informed!

 

[TiggR]

I have encountered a similar problem with combo boxes but thought it was just me going mad. I had an SQL statement with a sub query in it which worked, but whenever I viewed the form I would always get an error because the SQL statement had changed and become invalid. It seems A2K tried to validate it and changed the statement. I dont think it liked the sub query.

If you do find a reason for this behaviour please let me know. But I can assure you you are not going mad, just as you have assured me I am not going mad.

Doug