Re: Split DB application and file sizes

On May 5, 8:26 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
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:www.DataDevilDog.BlogSpot.com,www.DatabaseTips.BlogSpot.comhttp://www.Access.QBuilt.com/html/expert_contributors2.htmlfor contact
info.

"Stan" <stanha...@xxxxxxxxxxx> wrote in message

news:1178409159.628507.168380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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

.

Relevant Pages

  • Re: access 2003
    ... I would focus on the queries behind the combo boxes. ... the Access 97 database, I wouldn't have thought any expressions would be ... When you select a customer and a job in the two combo boxes, ...
    (microsoft.public.access.conversion)
  • Re: access 2003
    ... I would focus on the queries behind the combo boxes. ... the Access 97 database, I wouldn't have thought any expressions would be ... When you select a customer and a job in the two combo boxes, ...
    (microsoft.public.access.conversion)
  • Re: Question on conversion to ADP
    ... the money toward developping .NET technologies instead of Access. ... result of passthrough queries read/write instead of read only and also make ... database become corrupted when the users will start making their very own ... of ADP but what they are pushed toward is - how could I say that politely - ...
    (microsoft.public.access.adp.sqlserver)
  • Re: query design appears to be overwritten - how, why?
    ... To correct it, make sure all other users are out of the database, and follow ... Compact the database to get rid of this junk: ... The queries draw ... I have saved, closed the query, opened it again and observed ...
    (microsoft.public.access.queries)
  • Re: Forms corrupting - so will create new FE - please tell me gotc
    ... You must create and maintain relationships in the database that contains the actual tables You cannot create a relationship with referential integrity between attached tables in the front end. ... When you create queries in the front end, it actually reads the relationships from the back end to decide how to join the tables. ... Compact, then decompile, then compact your existing database. ...
    (microsoft.public.access.formscoding)