Trying to create a similar database

I'm brand new to Access, and I only have Access 2000.

I work for a large roofing company. We would like to track our bids to
general contractors, municipal entities, etc. by using an Access database.

One of our estimators brought with him, from his former job, a database
utilized similarly at his old job. It, of course, was protected and we
cannot edit it to our specifications.

I was able to create a new database by mimicking the tables, queries, forms,
etc. from the existing database. The new Bid Log, of course, does not
function properly. I'm aware that there certainly must have been OLE
objects, etc. that won't apply in the new database. I didn't expect that
this new database would function properly on the first time out.

I could really use some help in identifying where my missing links are. If
someone's willing to respond, I will begin posting questions.

Thank you very much for this valuable resource.

Go ahead and post a few questions. While you're at it, here are a few
points about which people will surely wonder: How did you go about
mimicking the other database? Did you mimic the Relationships from the
other database?
When posting your questions, it will help to keep them fairly simple at
first. Start with the structure, and a description of any terms that may
not be widely understood. For instance, Bid is clear enough, but other
terms may not be.

"Betty" wrote in message
...
I'm brand new to Access, and I only have Access 2000.

I work for a large roofing company. We would like to track our bids to
general contractors, municipal entities, etc. by using an Access database.

One of our estimators brought with him, from his former job, a database
utilized similarly at his old job. It, of course, was protected and we
cannot edit it to our specifications.

I was able to create a new database by mimicking the tables, queries,
forms,
etc. from the existing database. The new Bid Log, of course, does not
function properly. I'm aware that there certainly must have been OLE
objects, etc. that won't apply in the new database. I didn't expect that
this new database would function properly on the first time out.

I could really use some help in identifying where my missing links are.
If
someone's willing to respond, I will begin posting questions.

Thank you very much for this valuable resource.

GREAT! Thank you.

First, let me explain how I mimicked the original, replicated, LOCKED-UP
database:

I opened it, and even though it told me that it was read-only, I continued
through every table, query, form, relationship, etc. and created identical
paths and similar language in a new, fully-editable database.

I'm sure that some of my problems are coming from areas of the database that
depended upon information accessed from that original company's files. OLE
objects or other linked files which, of course, don't exist here at my
company.

Quite a bit of the empty database works as it should. There were portions
of the original (BidLog 1) that remained locked, and I was unable to dig
around and mimick their properties or functions.

I guess, first of all, is there a way to unlock a replicated database?
Also, what does the figure 8 on it's side represent? I'm seeing that often
in the relationship and query areas.




"BruceM" wrote:

Go ahead and post a few questions. While you're at it, here are a few
points about which people will surely wonder: How did you go about
mimicking the other database? Did you mimic the Relationships from the
other database?
When posting your questions, it will help to keep them fairly simple at
first. Start with the structure, and a description of any terms that may
not be widely understood. For instance, Bid is clear enough, but other
terms may not be.

"Betty" wrote in message
...
I'm brand new to Access, and I only have Access 2000.

I work for a large roofing company. We would like to track our bids to
general contractors, municipal entities, etc. by using an Access database.

One of our estimators brought with him, from his former job, a database
utilized similarly at his old job. It, of course, was protected and we
cannot edit it to our specifications.

I was able to create a new database by mimicking the tables, queries,
forms,
etc. from the existing database. The new Bid Log, of course, does not
function properly. I'm aware that there certainly must have been OLE
objects, etc. that won't apply in the new database. I didn't expect that
this new database would function properly on the first time out.

I could really use some help in identifying where my missing links are.
If
someone's willing to respond, I will begin posting questions.

Thank you very much for this valuable resource.

The eight on its side is the infinity symbol, used when creating
relationships between tables. It represents the "many" side of a
one-to-many relationship. For instance, each bid is for a single customer,
but you may make many separate bids for a customer. Therefore the
relationship between Customers and Bids is one-to-many. In a database than
involves numberous other entities (sales, subcontractors, or whatever) it
can become quite a bit more complex, so one of the questions is about the
real-life situation behind the database.
What does the BidLog do? Can you provide some bare-bones sample data or
output?
I know very little about unlocking a locked database; furthermore, if you
are working from a replicated copy it brings additional questions into the
mix, that I am unable to answer. In any case, here on the Atlantic coast of
the US I am about to leave for the day, so I hope others jump in before I
return to my desk.

"Betty" wrote in message
...
GREAT! Thank you.

First, let me explain how I mimicked the original, replicated, LOCKED-UP
database:

I opened it, and even though it told me that it was read-only, I continued
through every table, query, form, relationship, etc. and created identical
paths and similar language in a new, fully-editable database.

I'm sure that some of my problems are coming from areas of the database
that
depended upon information accessed from that original company's files.
OLE
objects or other linked files which, of course, don't exist here at my
company.

Quite a bit of the empty database works as it should. There were portions
of the original (BidLog 1) that remained locked, and I was unable to dig
around and mimick their properties or functions.

I guess, first of all, is there a way to unlock a replicated database?
Also, what does the figure 8 on it's side represent? I'm seeing that
often
in the relationship and query areas.




"BruceM" wrote:

Go ahead and post a few questions. While you're at it, here are a few
points about which people will surely wonder: How did you go about
mimicking the other database? Did you mimic the Relationships from the
other database?
When posting your questions, it will help to keep them fairly simple at
first. Start with the structure, and a description of any terms that may
not be widely understood. For instance, Bid is clear enough, but other
terms may not be.

"Betty" wrote in message
...
I'm brand new to Access, and I only have Access 2000.

I work for a large roofing company. We would like to track our bids to
general contractors, municipal entities, etc. by using an Access
database.

One of our estimators brought with him, from his former job, a database
utilized similarly at his old job. It, of course, was protected and we
cannot edit it to our specifications.

I was able to create a new database by mimicking the tables, queries,
forms,
etc. from the existing database. The new Bid Log, of course, does not
function properly. I'm aware that there certainly must have been OLE
objects, etc. that won't apply in the new database. I didn't expect
that
this new database would function properly on the first time out.

I could really use some help in identifying where my missing links are.
If
someone's willing to respond, I will begin posting questions.

Thank you very much for this valuable resource.

On Tue, 20 Feb 2007 12:57:13 -0800, Betty
wrote:

GREAT! Thank you.

First, let me explain how I mimicked the original, replicated, LOCKED-UP
database:

I opened it, and even though it told me that it was read-only, I continued
through every table, query, form, relationship, etc. and created identical
paths and similar language in a new, fully-editable database.

You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.

I'm sure that some of my problems are coming from areas of the database that
depended upon information accessed from that original company's files. OLE
objects or other linked files which, of course, don't exist here at my
company.

These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?

Quite a bit of the empty database works as it should. There were portions
of the original (BidLog 1) that remained locked, and I was unable to dig
around and mimick their properties or functions.

I guess, first of all, is there a way to unlock a replicated database?
Also, what does the figure 8 on it's side represent? I'm seeing that often
in the relationship and query areas.

If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".


John W. Vinson [MVP]

"John W. Vinson" wrote:


You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.

This solution did not work, because since the database was protected from
the start, any copies were already "replicated" copies.


These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?

Ok, this I knew...but I'm not to the point where I can really see what files
need to be linked. I need to get this thing working first.

If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".

What I'm working on is no longer a replica. It is a brand new database that
I'm trying to create by duplicating the commands from the other "replicated"
one.

The tip you've given me from "Help" would have worked, maybe.
Unfortunately, I'm a brand new Access user, and it's a bit advanced for me.

I will continue in the direction I've been going. When I hit the areas that
just stump me completely, I'll post new questions. I'd appreciate additional
help if anyone can lend it.

First new question: Can someone put in layman's terms for me the S_GUID
notations I'm seeing throughout the original replica?

Thank you so much!

Where are you seeing the S_GUID notations? I don't recognize it as an
Access term, so I expect it is specific to your database. It may be the
name of a table or query. Are there any table or queries by that name?

Here are some links that may help you understand some of the concepts and
terminology:
http://allenbrowne.com/tips.html

Look first at the Tips for Casual Users, particularly:
http://allenbrowne.com/casu-01.html
http://allenbrowne.com/casu-06.html

"Betty" wrote in message
news


"John W. Vinson" wrote:


You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.

This solution did not work, because since the database was protected from
the start, any copies were already "replicated" copies.


These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?

Ok, this I knew...but I'm not to the point where I can really see what
files
need to be linked. I need to get this thing working first.

If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".

What I'm working on is no longer a replica. It is a brand new database
that
I'm trying to create by duplicating the commands from the other
"replicated"
one.

The tip you've given me from "Help" would have worked, maybe.
Unfortunately, I'm a brand new Access user, and it's a bit advanced for
me.

I will continue in the direction I've been going. When I hit the areas
that
just stump me completely, I'll post new questions. I'd appreciate
additional
help if anyone can lend it.

First new question: Can someone put in layman's terms for me the S_GUID
notations I'm seeing throughout the original replica?

Thank you so much!

They mention S_GUID in the "help" area under making a replicated database a
regular database.

I saw the S_GUID notations SOMEWHERE when I was digging around in the
database. Unfortunately, I cannot find them at the moment.

Ugh. Ok, I'm still digging. Thanks for your attention.

"BruceM" wrote:

Where are you seeing the S_GUID notations? I don't recognize it as an
Access term, so I expect it is specific to your database. It may be the
name of a table or query. Are there any table or queries by that name?

Here are some links that may help you understand some of the concepts and
terminology:
http://allenbrowne.com/tips.html

Look first at the Tips for Casual Users, particularly:
http://allenbrowne.com/casu-01.html
http://allenbrowne.com/casu-06.html

"Betty" wrote in message
news


"John W. Vinson" wrote:


You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.

This solution did not work, because since the database was protected from
the start, any copies were already "replicated" copies.


These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?

Ok, this I knew...but I'm not to the point where I can really see what
files
need to be linked. I need to get this thing working first.

If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".

What I'm working on is no longer a replica. It is a brand new database
that
I'm trying to create by duplicating the commands from the other
"replicated"
one.

The tip you've given me from "Help" would have worked, maybe.
Unfortunately, I'm a brand new Access user, and it's a bit advanced for
me.

I will continue in the direction I've been going. When I hit the areas
that
just stump me completely, I'll post new questions. I'd appreciate
additional
help if anyone can lend it.

First new question: Can someone put in layman's terms for me the S_GUID
notations I'm seeing throughout the original replica?

Thank you so much!

Betty wrote:
They mention S_GUID in the "help" area under making a replicated database a
regular database.

I saw the S_GUID notations SOMEWHERE when I was digging around in the
database. Unfortunately, I cannot find them at the moment.

Ugh. Ok, I'm still digging. Thanks for your attention.

"BruceM" wrote:

Where are you seeing the S_GUID notations? I don't recognize it as an
Access term, so I expect it is specific to your database. It may be the
name of a table or query. Are there any table or queries by that name?

Here are some links that may help you understand some of the concepts and
terminology:
http://allenbrowne.com/tips.html

Look first at the Tips for Casual Users, particularly:
http://allenbrowne.com/casu-01.html
http://allenbrowne.com/casu-06.html

"Betty" wrote in message
news

"John W. Vinson" wrote:

You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.
This solution did not work, because since the database was protected from
the start, any copies were already "replicated" copies.


These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?
Ok, this I knew...but I'm not to the point where I can really see what
files
need to be linked. I need to get this thing working first.
If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".

What I'm working on is no longer a replica. It is a brand new database
that
I'm trying to create by duplicating the commands from the other
"replicated"
one.

The tip you've given me from "Help" would have worked, maybe.
Unfortunately, I'm a brand new Access user, and it's a bit advanced for
me.

I will continue in the direction I've been going. When I hit the areas
that
just stump me completely, I'll post new questions. I'd appreciate
additional
help if anyone can lend it.

First new question: Can someone put in layman's terms for me the S_GUID
notations I'm seeing throughout the original replica?

Thank you so much!


That field and a couple of others are added as unique record identifiers
when a database is replicated. They a normally hidden fields.

gls858

My mistake. Here is some information I found:

Whan a database is replicated, Microsoft Access adds the
following system fields to each replicated table in the replicated database:

Field Description
s_GUID A globally unique identifier for each record.
s_Lineage A binary field that contains information about the
history of
changes to each record.
s_Generation A field that stores information regarding groups of
changes.

As I understand it, you are working with a replica if you see these fields
in your tables. You can check by going to View Options and selecting the
check box to show system objects.

"Betty" wrote in message
news
They mention S_GUID in the "help" area under making a replicated database
a
regular database.

I saw the S_GUID notations SOMEWHERE when I was digging around in the
database. Unfortunately, I cannot find them at the moment.

Ugh. Ok, I'm still digging. Thanks for your attention.

"BruceM" wrote:

Where are you seeing the S_GUID notations? I don't recognize it as an
Access term, so I expect it is specific to your database. It may be the
name of a table or query. Are there any table or queries by that name?

Here are some links that may help you understand some of the concepts and
terminology:
http://allenbrowne.com/tips.html

Look first at the Tips for Casual Users, particularly:
http://allenbrowne.com/casu-01.html
http://allenbrowne.com/casu-06.html

"Betty" wrote in message
news


"John W. Vinson" wrote:


You might have missed a much simpler solution...! If the database had
at some point been copied to a CD or DVD disk, Windows would mark the
file as "read only". This setting can be turned off by looking at the
file in Windows Explorer, right mouse clicking it, selecting
Properties, and unchecking the "Read Only" box.

This solution did not work, because since the database was protected
from
the start, any copies were already "replicated" copies.


These of course would need to be either deleted or replaced with your
own files - are these graphics objects, such as company logo or
letterheads?

Ok, this I knew...but I'm not to the point where I can really see what
files
need to be linked. I need to get this thing working first.

If this is a Replica of a replicated database, it can be
"unreplicated" with a fair bit of fiddly work. Check Access Help topic
"Make a replicated database a regular database".

What I'm working on is no longer a replica. It is a brand new database
that
I'm trying to create by duplicating the commands from the other
"replicated"
one.

The tip you've given me from "Help" would have worked, maybe.
Unfortunately, I'm a brand new Access user, and it's a bit advanced for
me.

I will continue in the direction I've been going. When I hit the areas
that
just stump me completely, I'll post new questions. I'd appreciate
additional
help if anyone can lend it.

First new question: Can someone put in layman's terms for me the
S_GUID
notations I'm seeing throughout the original replica?

Thank you so much!