Relationships

Q

Question Boy

Hello,

Could someone please enlighten me!

If I split my database. where should table relationships be created (be, fe
or both)?

If there are relationshiops created in both the be and fe, but different
one, which ones are used to govern the database behavior when in the fe? I
assume the fe's relationships, but assumption is the...... so I thought I'd
ask.

Is there a simple article or ressource that could clarify this a bit better
for me?

Thank you!

QB
 
V

vbasean

Hello,

Could someone please enlighten me!

If I split my database.  where should table relationships be created (be, fe
or both)?

If there are relationshiops created in both the be and fe, but different
one, which ones are used to govern the database behavior when in the fe? I
assume the fe's relationships, but assumption is the...... so I thought I'd
ask.

Is there a simple article or ressource that could clarify this a bit better
for me?

Thank you!

QB

I try to do my normalizing in the back end

there are some things I feel I have to handle from the user end and
there are local tables in my user front end that are look up tables
and user specific data.

my opinion is it's not a black and white question.
 
A

aaron.kempf

come on sean.. Access doesn't support client-server, let alone n-tier.

-Aaron
 
A

aaron.kempf

SQL Server is where the relationships should be maintained.

then you don't need to worry about it.

-Aaron
 
V

vbasean

what you're talking about is n-teir application basics

I would suggest getting a copy of this book "Beggining Access VBA
2003"  Denise does a good job explaining n-teir logic.

http://www.amazon.com/Beginning-Access-2003-VBA/dp/B000QEXCNW/ref=sr_...

I think the poster wants basics. A split database is an n-teir
database. It's just a 2-teir. The concepts are the same.

The poster needs to grasp the basics of a 2-teir system.

back end with data and structure

front end combined with business logic.

That's all I was trying to point out in a nutshell.
 
Q

Question Boy

SQL Server? I am using Ms Acces. I'm confused. Even more now. Should they
be in the front or back end of the database. Which one drives the integrity
of the application? One, both..?
 
V

vbasean

SQL Server?  I am using Ms Acces.  I'm confused.  Even more now.  Should they
be in the front or back end of the database.  Which one drives the integrity
of the application?  One, both..?






- Show quoted text -

this is an MS Access forum so, I'll stick with an MS Access answer

create a back end with your tables

create your relationships in this back end database

create a separate front end

link the tables from your back end

create your forms etcetera

then, you can copy this front end to other stations and

at my office, it really works... lol

yes, access works for an multi station set up. I administer it every
day
 
A

aaron.kempf

SQL Server drives the integrity of the application.

If you put it in SQL Server; you don't have to worry about frontend vs
backend.

With SQL Server, you can edit a table-- you can add a query-- while
people are _IN_ the database.

-Aaron
 
A

aaron.kempf

Dude you're a ****ing jackass you know that?

nTier is not the same as client server.
nTier is not the same as client server.
nTier is not the same as client server.
nTier is not the same as client server.
nTier is not the same as client server.
nTier is not the same as client server.
nTier is not the same as client server.

and for the _FACTS_ of the matter-- Access doesn't allow nTier _OR_
client server.

Access Data Projects are truly client-server. The best way to keep
your data reliable, secure, available-- keep it in a database server.

Splitting into a front end / back end is no longer the reccomended way
of working with MS Access.

It hasn't been that way for almost a decade.

-Aaron
 
A

aaron.kempf

Access might work for a multi-station set up _UNTIL_ someone uses
Wireless
VPN
Internet
WAN

Access database don't work on any of those platforms.

SQL Server _DOES_.

Access might work for a multi-station set up _UNTIL_ some script kid
learns SQL Server.

SQL Server is better, faster, more reliable..

AND THE PUNCHLINE IS THAT IT IS EASIER ALSO
 
A

aaron.kempf

and for the record? I'm not saying that Access is 'bad'.

I'm just saying that anyone using it as a database should be out of a
job.

Access is merely a front end to SQL Server.
No more and no less.

-Aaron
 
V

vbasean

aaron,

first, I'm not your enemy.

second, this is an MS Access forum. Not a soap box for what's a
better database solution.

third, Access is a fine solution for small business split database
operations.

forth, with all due respect, let's not hijack peoples threads. ok?
 
A

aaron_kempf

I'm not hijacking jack shit.

I'm reccomending SQL Server, because it is better, faster, simpler.

End of story--

And _YES_ this is a soap box-- where I am reccomending that people use
a) existing forms and reports
b) the most popular desktop / enterprise database anywhere. (that
refers to SQL Server).
c) best practices
d) centralization of business logic
e) existing tools-- instead of a piece of crap DAO database.
f) existing tools - SQL Agent - instead of batch files.

Sorry that you're stuck making $12/hour. That doesn't mean that
everyone else in this forum should be stuck using a 1980s style
database.

-Aaron
 
D

Daniel Pineault

I don't want to get into a long discussion on the topic, but some of your
statements are false.

I have used access very succesfully over VPN and WAN. It depends on your
network more than anything else. I'm not saying there aren't better
alternatives, but it can be done. Citrix also works great, in my experience.

Daniel Pineault
 
D

Daniel Pineault

Aaron who peed in your cereals this morning! Really!

Making such broad statement says a lot about you. Do you have no concept of
the number of companies for which Access is an ideal solution! You don't
need to use a bazooka to kill a bird. Every situation needs to be properly
analyzed. Small business, individuals, class projects, and so much
more....Access is the ideal answer. One way or another, Access is 1,000,000%
better than what most companies do by using Excel as their database.

Why do you come to an Access newsgroup if your are just bad mouthing the
product in question.

Daniel Pineault
 
G

Gina Whipp

Question Boy,

Relationships go where the actual tables are in the back-end. For lack of a
better way to say it... when you split a database you SEE the relationships
in the front end but that's only a mirror of what's in the back-end.

On another note, please ignore Aaron, his solution for EVERYTHING is a SQL
Server.
 
V

vbasean

I don't know why I'm continuing this but...

the cheapest version of SQL Server is ...

$4000

this does not include a front end solution
you'll have to pay someone to create this from most likely Visual
Studio

Rough estimate on front end cost

$4000


MS Office Complete...
front end and back end with integration into Excel, Word, Power Point
etcetera

$400

Someone to genuinely create a solution for a small business (4 to 5
stations) with Access...

$4000 - $5000

or hire someone with advanced skills in MS Access $45,000 a year.
 
Q

Question Boy

Gina,

You must have been reading my mind. This is exactly where my question was
originating from. When I split the db I ended up with relationships in both
the be and the fe.

So the proper approach is to make updates to the relationships in the
back-end (from what I understand - excludling local table, which I have none
in this case).

Should I delete the mirror relationships in the front-end?

Thank you for the help!
 
G

Gina Whipp

Question Boy,

I have never deleted the ones in the front-end. I leave them because in
case I want to peak at them I don't have to go to the back-end. However,
it's up to you if you want to delete them.

Glad to help!
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top