Using Objects from one database in another database

How mature...

On Apr 26, 4:01 pm, "Aaron Kempf" wrote:
well I'm so sorry that you chose the wrong database

'its far too advanced'

gag me with a spoon.. I can convert _ANY_ MDB to a well tuned ADP solution
in a week or two

"Josetta" wrote in message

oups.com...



Sorry, but this is not an option. I'm not even sure what Access Data
Projects is, but the database is far too advanced to make any sort of
switch.

On Apr 25, 8:13 pm, "Aaron Kempf" wrote:
if you used Access Data Projects, then it would be quite easy to share
data
in between databases

it would take ZERO code and ZERO effort

you just would need to add database.schema.object

schema is typcially 'dbo' for SQL 2000.. in SQL 2005; it'll break more
into
a ROLE type.. like Accounting, HR, Recruiting, Manufacturing, etc

but seriously
make your life easier-- move to Access Data Projects

"Josetta" wrote in message

roups.com...

I've looked around here to see if this can be done, but haven't found
the answer. Here is what I want to do...

I have a two databases -- One for Sales and one for Operations. These
are used by two groups of people with some obvious overlap (like the
boss, for example). Some of the data is the same, so I'm using only
one backend database file to hold the data. However, I want to have
one piece (projects) from the Operations database to also be used in
the sales database. The projects piece of it consists of several
forms, subforms, reports, queries, code, etc.

To cut down on maintenance (so without actually importing) I want to
be able to use those forms, subforms, etc. in the Sales database,
exactly as they are in the Operations database.

Is there a way to do this so that any changes made in the Operations
database are also reflected in the Sales database? I've never created
Add-ins before, but before I go trying to make this happen, is this
the way I need to go? Would this even work? I guess what I'm saying
is I want to link code, forms, reports, etc. just like I can link
tables.

Any ideas?- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

Tony,

Thanks for your suggestions and for reinterating to Aaron that,
whatever his agenda, he (probably) didn't read and certainly didn't
understand my issue.

Josetta

On Apr 27, 5:19 pm, "Tony Toews [MVP]" wrote:
"Aaron Kempf" wrote:
and that API is unnecessary

Select SUSER_SNAME() gives you the name of the current user in ADP

And totally irrelevant in an MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm

Josetta wrote:

Thanks for your suggestions and for reinterating to Aaron that,
whatever his agenda, he (probably) didn't read and certainly didn't
understand my issue.

You are quite welcome.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm