This allows for multiple people to be in the same system and input and view
ONLY their own records.
So the table is the source, the query provides the filter/view, and the form
is the interface.
My problem is that the form (because of the query) won't allow new records
in SQL.
Only the tables were upsized. The Access DB has not changed. The tables
are now linked tables.
A regular user can input new records into the source table directly, but not
through the query.
The table is on a SQL server, the query and form are in an Access
application.
I want to assume that the problem is the CurrentUser() command not working
in SQL, but what would I replace it with, and why should I have to, seeing
that the default value is located in the Access form and not in the SQL
table.
Thanks beforehand
see my answer in microsoft.public.access.forms.
When posting the same message in more than one newsgroup use crossposts
and an appropriate follow-up. So that others can find my answer.
mfG
--> stefan <--
"Stefan Hoffmann" <ste...@ste5an.de> wrote in message
news:evpCajjW...@TK2MSFTNGP02.phx.gbl...
Jacques Latoison wrote:
> I initially did the other post as I assumed no one was going to answer.
> However, what is a crosspost?
http://en.wikipedia.org/wiki/Crossposting
http://www.webhero.org/Newsgroups/crossposting.asp
mfG
--> stefan <--
Can you possibly tell me where to find your? I think this wil help with my
recent post "Some subforms work some don't".
I know it would have been best if Jacques had posted the link but since he
didn't can you help.
-Mark-
--
Mark Annett
ISPManSys.com
"Stefan Hoffmann" wrote:
> .
>
Mark Annett wrote:
> Can you possibly tell me where to find your? I think this wil help with my
> recent post "Some subforms work some don't".
mfG
--> stefan <--
"Stefan Hoffmann" wrote:
> .
>