<div>
With no code, you leave us guessing. 
However, it doesn't make that much difference, as your code should definitely not require you to switch between design view and form view. 
 
You need to rethink your concept. 
 
/gustav
</div>

<div>
Yes, ...I too am confused by your &quot;workflow&quot; here. 
 
Can you explain to us, ...with explicit details, exactly what this system is trying to do? 
 
Perhaps there is a more efficient approach...
</div>

<div>
I am an apprentice in software development, so sorry if my description doesn't make sense. 
 
So I have a form called form1, which has within it 3 sub forms: visit_by_job_replacement, by_job, equipment_needed. What I am trying to explain is in the sub form visit_by_job_replacement you can choose, from a drop down, a number of job codes. When you choose one of these job codes, the by_job and the equipment_needed is meant to change, which it does at the moment. 
 
However, when i was changing from form view to design view and back. I noticed that it had stopped working, at this moment I was quite confused and went into procedure code and had a play around and noticed when I changed the id from a string to a variant it worked. So I went back and did the same thing, changed it from form view to design view and back. Again it stopped working so i changed the variant back to a string and it worked. I'm not sure if its a bug with access but it happens everytime i change from form to design and back. 
 
The procedure code that I have is as follows: 
 
visit_by_job1-Form_by_job(Code) 
 
Public Function setParent(parent_id As Variant) 
If parent_id = &quot;&quot;&nbsp;Then parent_id = &quot;0&quot; 
Me.RecordSource = &quot;select * from visit_by_job_replacement_c where parent_record_id = &quot;&nbsp;&amp; parent_id 
Me.Requery 
If Not (IsNull(Me!id)) Then Form_equipment_needed.setParent (Me!id) 
End Function 
-------------------------------------------------------------------------------------------------------------------------------------------- 
Visit_by_Job1 - Form_equipment_needed(Code) 
 
Public Function setParent(id As Variant) 
If id = &quot;&quot;&nbsp;Then id = &quot;0&quot; 
Me.RecordSource = &quot;select * from visit_next_visit_next_equipment_needed_c where parent_record_id = &quot;&nbsp;&amp; id 
Me.Requery 
 
End Function 
------------------------------------------------------------------------------------------------------------------------------------ 
Visit_by_job1 - Form_visit_by_job_replacement(Code) 
 
Private Sub Form_Current() 
If Not (IsNull(Me!id)) Then Form_by_job.setParent (id) 
 
 
 
End Sub 
---------------------------------------------------------------------------------------------------------------------------------------------- 
 
I hope this helps in solving my problem. Even the IT specialists that have worked here for more than two years are confused as to whats going on with access. 
 
Thanks.
</div>

<div>
Sounds like you - after a design change - should compile and save, close the form, and reopen it. 
 
/gustav
</div>

<div>
It comes up with would you like to save these changes. I click yes go back into the form, and its exactly the same. It just breaks, until I click on a field that has a null value then it seems that the code starts to make a difference and change the other subforms.
</div>

<div>
Try this modification: 

<pre><code class="code-1 nolinks" id="code-20-41519028-1">Public Function setParent(id As Variant)

 Me.RecordSource = &quot;select * from visit_next_visit_next_equipment_needed_c where parent_record_id = &quot; &amp; Val(Nz(id)) &amp; &quot;&quot;

End Function
</code></pre>
The requery should not be needed. 
 
/gustav
</div>

<div>
No there is no change, still does the same thing.
</div>

<div>
Then it has nothing to do with this code. Something else is going on. 
 
If what you want is to sync the subforms, you may get some inspiration here: 
 
<a href="http://rdsrc.us/TzJyLQ" rel="ugc">Synchronizing Multiple Subforms in Access</a> 
 
/gustav
</div>

<div>
You are welcome! 
 
/gustav
</div>

<div>
<div class="content wysiwyg-content">
In Access 2013, I have a form. this form takes a database and links it to another database. So that you can choose a code in a drop down menu and it will show the relative information in the other tables. When I switch from normal view to design view and then back to normal view. The procedure code seems to break and it doesn't show the information when I change the code. It will only work when I keep changing the variant to be a string in the procedure code, but it will break everytime i change the view.
</div>
</div>

In Access 2013, I have a form. this form takes a database and links it to another database. So that you can choose a code in a drop down menu and it will show the relative information in the other tables. When I switch from normal view to design view and then back to normal view. The procedure code seems to break and it doesn't show the information when I change the code. It will only work when I keep changing the variant to be a string in the procedure code, but it will break everytime i change the view.

How do I fix my procedure code in Access 2013?

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.