By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,404 Members | 2,300 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,404 IT Pros & Developers. It's quick & easy.

Split DB application and file sizes

P: n/a


I am working on a database in ACCESS 2003. This is a simple DB with
only one table. I have split the DB so I can upgrade and debug the
front end before installing on my clients' computer. I used the
ACCESS splitter utility and everything appeared to go OK. If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms. but, I also see the Table. If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table. When I look at the size of the
files, the front end file is the same size as the original un-split
database.

Can someone explain what is happening ?

Thanks,

Stan Hanna

May 5 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
splitting the DB allows you to work on the forms, reports, etc in a copy of
the front end, while a user still uses the DB, then you over write the FE
and no data in the tables is lost
"Stan" <st*******@hotmail.comwrote in message
news:11**********************@w5g2000hsg.googlegro ups.com...
>

I am working on a database in ACCESS 2003. This is a simple DB with
only one table. I have split the DB so I can upgrade and debug the
front end before installing on my clients' computer. I used the
ACCESS splitter utility and everything appeared to go OK. If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms. but, I also see the Table. If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table. When I look at the size of the
files, the front end file is the same size as the original un-split
database.

Can someone explain what is happening ?

Thanks,

Stan Hanna

May 6 '07 #2

P: n/a
Hi, Stan.
Can someone explain what is happening ?
Sure.
If I run
"Copy of DB_be.mdb"
This is because you're working with the first "copy of" the file, rather
than the original.
If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
Then it's working as designed. If you had multiple tables with
relationship, that's where the relationships would migrate, also.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms.
Then it's working as it should.
but, I also see the Table.
Not exactly. You see the link to the table located in the back end. Take a
closer look at the icon in the Database Window. Does it have a blue
right-pointing arrow on the left of the table icon? If so, that indicates a
link to the actual table, because the table no longer resides in the front
end after the database was split with the wizard.
If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table.
You removed the link to the table in the back end, so how is the query going
to find the table? Link to the table in the back end again and use the same
name for the table, and your queries in the front end will work again.
When I look at the size of the
files, the front end file is the same size as the original un-split
database.
The table was taking up space when it was there, but now that it's gone that
space isn't reclaimed until one does a compact/repair on the database file.
Select the Tools -Database Utilities -Compact and Repair Database...
menu in the front end open, and it will reclaim the disk space that was once
used for the table, making the file smaller. Periodically, you'll need to
compact and repair the back end, too, to reclaim the disk space as the table
is used.

Therefore, your database was working as designed, and you needn't worry as
long as you relink the table and compact the database periodically.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"Stan" <st*******@hotmail.comwrote in message
news:11**********************@w5g2000hsg.googlegro ups.com...
>

I am working on a database in ACCESS 2003. This is a simple DB with
only one table. I have split the DB so I can upgrade and debug the
front end before installing on my clients' computer. I used the
ACCESS splitter utility and everything appeared to go OK. If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms. but, I also see the Table. If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table. When I look at the size of the
files, the front end file is the same size as the original un-split
database.

Can someone explain what is happening ?

Thanks,

Stan Hanna

May 6 '07 #3

P: n/a
On May 5, 8:26 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@Spameater.orgZERO_SPAMwrote:
Hi, Stan.
Can someone explain what is happening ?

Sure.
If I run
"Copy of DB_be.mdb"

This is because you're working with the first "copy of" the file, rather
than the original.
If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.

Then it's working as designed. If you had multiple tables with
relationship, that's where the relationships would migrate, also.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms.

Then it's working as it should.
but, I also see the Table.

Not exactly. You see the link to the table located in the back end. Take a
closer look at the icon in the Database Window. Does it have a blue
right-pointing arrow on the left of the table icon? If so, that indicates a
link to the actual table, because the table no longer resides in the front
end after the database was split with the wizard.
If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table.

You removed the link to the table in the back end, so how is the query going
to find the table? Link to the table in the back end again and use the same
name for the table, and your queries in the front end will work again.
When I look at the size of the
files, the front end file is the same size as the original un-split
database.

The table was taking up space when it was there, but now that it's gone that
space isn't reclaimed until one does a compact/repair on the database file.
Select the Tools -Database Utilities -Compact and Repair Database...
menu in the front end open, and it will reclaim the disk space that was once
used for the table, making the file smaller. Periodically, you'll need to
compact and repair the back end, too, to reclaim the disk space as the table
is used.

Therefore, your database was working as designed, and you needn't worry as
long as you relink the table and compact the database periodically.

HTH.
Gunny

Seehttp://www.QBuilt.comfor all your database needs.
Seehttp://www.Access.QBuilt.comfor Microsoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com...utors2.htmlfor contact
info.

"Stan" <stanha...@hotmail.comwrote in message

news:11**********************@w5g2000hsg.googlegro ups.com...
I am working on a database in ACCESS 2003. This is a simple DB with
only one table. I have split the DB so I can upgrade and debug the
front end before installing on my clients' computer. I used the
ACCESS splitter utility and everything appeared to go OK. If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms. but, I also see the Table. If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table. When I look at the size of the
files, the front end file is the same size as the original un-split
database.
Can someone explain what is happening ?
Thanks,
Stan Hanna
Thanks to All. I learned a lot tonight.

Stan Hanna

May 6 '07 #4

P: n/a
You're welcome. Good luck with the rest of the project.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"Stan" <st*******@hotmail.comwrote in message
news:11**********************@h2g2000hsg.googlegro ups.com...
On May 5, 8:26 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@Spameater.orgZERO_SPAMwrote:
>Hi, Stan.
Can someone explain what is happening ?

Sure.
If I run
"Copy of DB_be.mdb"

This is because you're working with the first "copy of" the file, rather
than the original.
If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.

Then it's working as designed. If you had multiple tables with
relationship, that's where the relationships would migrate, also.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms.

Then it's working as it should.
but, I also see the Table.

Not exactly. You see the link to the table located in the back end.
Take a
closer look at the icon in the Database Window. Does it have a blue
right-pointing arrow on the left of the table icon? If so, that
indicates a
link to the actual table, because the table no longer resides in the
front
end after the database was split with the wizard.
If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table.

You removed the link to the table in the back end, so how is the query
going
to find the table? Link to the table in the back end again and use the
same
name for the table, and your queries in the front end will work again.
When I look at the size of the
files, the front end file is the same size as the original un-split
database.

The table was taking up space when it was there, but now that it's gone
that
space isn't reclaimed until one does a compact/repair on the database
file.
Select the Tools -Database Utilities -Compact and Repair Database...
menu in the front end open, and it will reclaim the disk space that was
once
used for the table, making the file smaller. Periodically, you'll need
to
compact and repair the back end, too, to reclaim the disk space as the
table
is used.

Therefore, your database was working as designed, and you needn't worry
as
long as you relink the table and compact the database periodically.

HTH.
Gunny

Seehttp://www.QBuilt.comfor all your database needs.
Seehttp://www.Access.QBuilt.comfor Microsoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com...utors2.htmlfor
contact
info.

"Stan" <stanha...@hotmail.comwrote in message

news:11**********************@w5g2000hsg.googlegr oups.com...
I am working on a database in ACCESS 2003. This is a simple DB with
only one table. I have split the DB so I can upgrade and debug the
front end before installing on my clients' computer. I used the
ACCESS splitter utility and everything appeared to go OK. If I run
"Copy of DB_be.mdb" I see only the table, not the Queries or Forms.
When I run the front end "Copy of DB.mdb" I see the Queries and
Forms. but, I also see the Table. If I delete the table from the
front end and try to run a Query I receive the error message that the
application can not find the table. When I look at the size of the
files, the front end file is the same size as the original un-split
database.
Can someone explain what is happening ?
Thanks,
Stan Hanna

Thanks to All. I learned a lot tonight.

Stan Hanna

May 6 '07 #5

P: n/a
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM>
wrote in news:13*************@corp.supernews.com:
you needn't worry as
long as you relink the table and compact the database
periodically.
Front ends don't really need to be compacted. I never have my
clients do it. Ever.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
May 6 '07 #6

P: n/a
Hi, David.

Sorry. I didn't make that very clear. The front end needs to be compacted
after splitting the database with the wizard (to reclaim the space inside
the file that was previously occupied by the table), and the back end needs
to be compacted periodically.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"David W. Fenton" <XX*******@dfenton.com.invalidwrote in message
news:Xn**********************************@127.0.0. 1...
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AM>
wrote in news:13*************@corp.supernews.com:
> you needn't worry as
long as you relink the table and compact the database
periodically.

Front ends don't really need to be compacted. I never have my
clients do it. Ever.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

May 7 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.