tag:blogger.com,1999:blog-8134759511126815909.post3941160615381781223..comments2023-08-20T04:10:01.095-04:00Comments on <a href="http://rogersaccessblog.blogspot.com/">Roger's Access Blog</a>: Union Query: Part 2Roger Carlsonhttp://www.blogger.com/profile/12265719129831415014noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8134759511126815909.post-34084252885635690132012-03-05T07:02:53.403-05:002012-03-05T07:02:53.403-05:00Useful or not, it's one of the limitations of ...Useful or not, it's one of the limitations of Access SQL. <br /><br />As for solutions, there are probably several, depending on the specifics of your problem.<br /><br />But this is not the best venue for support. I suggest asking the question on Utter Access Forums<br /><a href="http://www.utteraccess.com" rel="nofollow"> www.utteraccess.com </a>Roger Carlsonhttps://www.blogger.com/profile/12265719129831415014noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-54729646279124435052012-02-29T17:15:10.985-05:002012-02-29T17:15:10.985-05:00I am really struggling trying to use a Union Query...I am really struggling trying to use a Union Query to input information in a form. I read your article "Recordset not updatable. Why?", and I am now puzzled with WHY NOT. It would be so useful to me to use the result of the Union Query as a querry for inputing into two tables at the same time, but this is simply impossible. So, why not? Is there a way to get around this?Khielhttps://www.blogger.com/profile/14380731511172656514noreply@blogger.com