multi user question

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

I have a form that creates a report from user input. It creates two
"temporary" tables and joins those table to ODBC linked tables. No
problem so far.

The client wants multiple users to run from that one database.

1) Could someone please verify that Access's answer to that is a front
end on each users workstation please so I can show that client

2) If I'm forced into this what's the best way to approach it? I've
thought of creating those temp table with the users ID appended to the
name of the table using "currentuser" or creating a db for the temp
tables on each user's local drive...

Ideas?

Jim
 
Regardless of this problem, each user should have their own copy of the front
end on their own computer. Multiple users sharing the same front end is
asking for corruption and since it has to be on a network shared folder,
doubling network traffic.

If you can convince the client this is the correct approach, then the tables
you use for the report can be in the front end, thus excluding the need for
any unnecessary filtering in the report. If the client insists on being an
idiot, then your plan to add a field to identify the user would be an
acceptable fall back position.
 
<snip> "If the client insists on being an idiot, then your plan to add a
field to identify the user" <snip>

Is that to say I could add a field to the existing table that would have
a "currentUser", then my report could be filtered by that field? My
thought was to create separate tables with that user name appended to
the field name but that's a lot more work than just filtering by a field
value. Multiple users (3 or 4 at best) appending to the same table is
not a problem?
 
<snip> "If the client insists on being an idiot, then your plan to add a
field to identify the user" <snip>

Is that to say I could add a field to the existing table that would have
a "currentUser", then my report could be filtered by that field? My
thought was to create separate tables with that user name appended to
the field name but that's a lot more work than just filtering by a field
value. Multiple users (3 or 4 at best) appending to the same table is
not a problem?
 
The answer is yes. Add a field to the table. As you add rows to the table
for that user, populate that field with the user name. Then use a query to
filter on the user's name fo rthe report. Be sure you clear out all records
with that user's name before you run a new report or you will get old stuff
mixed with the new. That is one line of code:

CurrentDb.Execute("DELETE * FROM MyTableName WHERE MyTableName.UserId = '" &
Me.UserName & "';"), dbFailOnError

Of course you will have to changes the names to suit your situation.

Now, it appears your client is insisting on playing with loaded guns on a
school playground. Here is a trick I use when the client is doing something
that could cause a serious (and this one definitely is) problem. I would
make them sign a waiver that politely, and in legalesse say "If I do it this
way and something bad happens and I don't have a current backup of my sytem,
then my software guy is not at fault. I choose not to listen to his
professional advise and the risk is all mine"

Good Luck
 
thanks - will do
The answer is yes. Add a field to the table. As you add rows to the table
for that user, populate that field with the user name. Then use a query to
filter on the user's name fo rthe report. Be sure you clear out all records
with that user's name before you run a new report or you will get old stuff
mixed with the new. That is one line of code:

CurrentDb.Execute("DELETE * FROM MyTableName WHERE MyTableName.UserId = '" &
Me.UserName & "';"), dbFailOnError

Of course you will have to changes the names to suit your situation.

Now, it appears your client is insisting on playing with loaded guns on a
school playground. Here is a trick I use when the client is doing something
that could cause a serious (and this one definitely is) problem. I would
make them sign a waiver that politely, and in legalesse say "If I do it this
way and something bad happens and I don't have a current backup of my sytem,
then my software guy is not at fault. I choose not to listen to his
professional advise and the risk is all mine"

Good Luck

:
Click to expand...
 
Back
Top