I have a recently-migrated-to-SQL database that is still using Access as the front end (which will be changing at some point in the indefinite future, but will remain for now).
For the most part, everything has gone just peachy, but there is one minor and annoying hitch: The Access search...
Alright, thanks. I don't mind going to additional lengths to secure the behavior I'm looking for, I just wanted to make sure, before doing so, that I wasn't doing something terribly wrong.
...and, actually, having tinkered with it further, it seems like this is simply how views work in general. I'm attaching an image to this to further explain what I'm getting at.
The view shown is:
SELECT dbo.Orders.OrderID, dbo.Orders.CustomerID, dbo.Customers.CustomerName
FROM...
I don't have the code handy (am at home, now), but it's pretty straight forward stuff. I have a pretty basic form using a query as a datasource. The query consists of a handful of fields from the order table and customer table, linked together by the customerID.
It's actually, having tinkered...
I'm in the midst of my first Access to SQL Server migration, and I have a question about form data sources.
I have a form that is used for entering and updating orders. In its, all-Access incarnation, the datasource for the form was a fairly straightforward query that worked more or less...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.