More than one person manage the the front-end

[Marco]

Hello.

Is it possibel to allow two users to manage the front-end database?

I mean, create and change the queries? I know that not changing at the same
time the same form or query or report or table.

But is it possible to access the same and create different things?

Regards,
Marco

 

[Calvin He]

Thx for sharing, but would u pls give us more details?

 

[Larry Linson]

To make design changes to a database, you must have it open for "Exclusive
Use". If the newly-created or newly-modified queries should be incorporated
for all users, then you do need to separate "design" and "use". The
concensus of experienced users is that you should split the database into
front-end and back-end, and each user should have a separate copy of the
front-end. There should also be a separate development copy, in which
design changes are made, and then a copy of that development copy
periodically released to all users as the production copy.

What you describe implies that you are not "managing" the development
process, and possibly that you have multiple users logging in to the same
copy of the front end. Both are recipes for "unpleasant surprises" and
should be avoided.

Larry Linson
Microsoft Office Access MVP

 

[Marco]

Hi.

No, I have one back-end and one front-end by user.

But, my partner and I need to develop several new things over the "original"
front-end so after we can change the users front-end so they can use this new
functions.

The problem is that I partner is using the original front-end and I have to
use a copy. Them I have to export everything to the orignal front-end to
integrate everything.


Marco

 

[John Spencer]

You might take a look at SourceSafe from MS.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

 

[a a r o n . k e m p f]

yes, you upsize to ADP, and then you can allow multiple people to work
on queries at the same time

 

[a a r o n _ k e m p f]

John;

you might want to look into ADP!

ADP does this perfectly, out of the box-- without any additional
software.

It's fucking disgusting to me that you call yourself a professional
and yet you don't know the basics of the best half of MS Access!
It's fucking disgusting to me that you call yourself a professional
and yet you don't know the basics of the best half of MS Access!
It's fucking disgusting to me that you call yourself a professional
and yet you don't know the basics of the best half of MS Access!

-Aaron

 

[GenlAccess]

yes, you upsize to ADP, and then you can
allow multiple people to work on queries
at the same time

And, too, if you are being paid to do the work, you will get paid all over
again before long, when Microsoft drops the obsolescent, outmoded, and all
but deprecated ADP model, and you get to re-implement.

General Access

 

[Tony Toews [MVP]]

Please ignore Aaron's reply as it has very, very little relevance to
your problem.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

Tony;

so-- what you're sayin is that ADP don't allow multiple developers to
edit / write queries at the same time?

Is that really what you're claiming??

Maybe you should try to understand the capabilities of the 'best half
of MS Access' before you either:
a) call yourself a professional
b) stalk me

 

[a a r o n _ k e m p f]

ADP isn't being depecrated. VBA is.

The bullshit loooping that you do in DAO on the clientside-- it's
quite easy to have all that logic in Stored Procedures, and with SQL
Server, we have error handling- on the database tier--that allows try
catch. This isn't available in Jet.

In SQL Server we can call native VB.net procedures / functions, etc.
Can you do this in Jet?

Keeping your logic- in one place- where it belongs- on a database
server- is just a better platform than a ton of spaghetti code.

Jet is just.. it's not designed from the ground up to work in a multi-
user environment.

-Aaron

 

[Tony Toews [MVP]]

b) stalk me

Please report my behavior to your local police department.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n _ k e m p f]

eat shit am I a nark?

I just think that it's funny that you claimed for the longest time
that you didn't do this.
You dipshits just got lucky.

It was illegal though.

-Aaron

 

[a a r o n _ k e m p f]

and for the record, there _ARE_ more than one agency has jurisdiction
over your international commercial espionage.

 

[a a r o n _ k e m p f]

and also-- why don't you apologize to me in public--

Because you know that ADP supports mutliple developers-- and Jet just
doesnt

So why is it that you continue to spread mis-information, faggot?

 

[Tony Toews [MVP]]

and for the record, there _ARE_ more than one agency has jurisdiction
over your international commercial espionage.

Excellent. Please report me to all of them.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[GenlAccess]

and also-- why don't you apologize to me in public--

Because you know that ADP supports mutliple developers-- and Jet just
doesnt

Access 2.0 supported multiple concurrent developers, and they learned that
was not a good idea, so the Access team eliminated it from MDB and, later,
ACCDB.

ADP was so little used, so limited, and so inconsequential in the scheme of
things that they didn't bother to fix it, just as they didn't bother to fix
ADP's other shortcomings.

I guess they figured that there would be some so obsessed that they'd claim
SQL Server's new features were ADP improvements, which of course they were
not. SQL Server just happens to be the back-end datastore you can use with
ADP; it also happens to be the ONLY back-end datastore you can use with ADP
(unlike MDB and ACCDB, which can link to a vast array of database engines).

Gen'l Access

 

[a a r o n . k e m p f]

ADP is the best platform, it is extremely popular.

but when strong database developers upsize from Jet to SQL, they move
to the SQL newsgroups.
Or the Reporting Services newsgroups.

Anyone that uses Jet for anything is stuck in the 2nd grade on the
technology ladder.

 

[a a r o n . k e m p f]

they _ARE_ ADP improvements.

When SQL Server gets more powerful-- ADP becomes more powerful.
That is one of the key benefits of ADP-- that it works with SQL
Server.

And Jet really doesnt'.

The # of steps to bind a form to a sproc (with 2 args for example) in
Jet plz.
Because I can do it with what, one mouse click?

-Aaron

 

[a a r o n . k e m p f]

re:
it also happens to be the ONLY back-end datastore you can use with
ADP

YES, YOU ARE CORRECT. I WILL GLADLY USE THE MOST POPULAR DATABASE IN
THE WORLD, AND I WILL NOT COMPLAIN.

It's a free database server-- and it's extremely faster than Jet.
Only a fucking retard, stuck in the 2nd grade-- woudl use jet for
anything.