Copied Reports won't save

[Josetta]

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.

['69 Camaro]

Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

Do you have the database file open exclusively? If not and other users are
connected to the front end, design changes can't be saved. If you have
SetWarnings off, you won't receive the warning that the object can't be
saved, IIRC.

It's best to split the database into a back end (tables and relationships)
and a front end (queries, forms, reports, et cetera), and then place the
back end on the shared network server and place a copy of the front end on
each user's workstation. For more information on splitting the database,
please see the "Split the Database" tip on the following Web page:

http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

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.
"Josetta" <Jo*****@smartdot.netwrote in message
news:11**********************@l77g2000hsb.googlegr oups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.

[Josetta]

No, This is not the problem. I have my own development file. It's
open exclusively. The group works on their own copy. There is a
front and back-end. This is simply a "glitch", I think; one that's
only been happening a few days. I routinely make copies of reports
and then edit them according to the new names. Only the past couple
of days has this been a problem.

On Mar 28, 2:53 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:

Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

Do you have the database file open exclusively? If not and other users are
connected to the front end, design changes can't be saved. If you have
SetWarnings off, you won't receive the warning that the object can't be
saved, IIRC.

It's best to split the database into a back end (tables and relationships)
and a front end (queries, forms, reports, et cetera), and then place the
back end on the shared network server and place a copy of the front end on
each user's workstation. For more information on splitting the database,
please see the "Split the Database" tip on the following Web page:

http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

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.

"Josetta" <[e-mail] in message

news:11**********************@l77g2000hsb.googlegr oups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.- Hide quoted text -

- Show quoted text -

['69 Camaro]

Hi, Josetta.

The group works on their own copy.

Unless this means "Each member of the group works with his own copy of the
front end," then it's being shared by more than one user, which is just as
effective as sharing a non-split database.

This is simply a "glitch", I think; one that's
only been happening a few days.

If it's corruption, then it's usually easy to get rid of by creating a new
database file, then importing the objects one group at a time, first the
tables, then the queries, then the forms, et cetera. Once everything is
imported, compile the code, then compact the database and see if you're
still having problems.

How big is the front end, by the way? You called it a monster database, but
the majority of the weight should be in the tables in the back end on the
server.

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.
"Josetta" <Jo*****@smartdot.netwrote in message
news:11**********************@p15g2000hsd.googlegr oups.com...

No, This is not the problem. I have my own development file. It's
open exclusively. The group works on their own copy. There is a
front and back-end. This is simply a "glitch", I think; one that's
only been happening a few days. I routinely make copies of reports
and then edit them according to the new names. Only the past couple
of days has this been a problem.

On Mar 28, 2:53 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:

>Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

Do you have the database file open exclusively? If not and other users
are
connected to the front end, design changes can't be saved. If you have
SetWarnings off, you won't receive the warning that the object can't be
saved, IIRC.

It's best to split the database into a back end (tables and
relationships)
and a front end (queries, forms, reports, et cetera), and then place the
back end on the shared network server and place a copy of the front end
on
each user's workstation. For more information on splitting the database,
please see the "Split the Database" tip on the following Web page:

http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

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.

"Josetta" <[e-mail] in message

news:11**********************@l77g2000hsb.googleg roups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.- Hide quoted text -

- Show quoted text -

[Josetta]

Gunny,

BTW, thank you for your quick replies.

There may be some corruption. The file is huge (typically around 50
megs at this point (compact), but it bloats-- still working on that)
and no, most of the weight is not in the tables (backend is around
25-30 megs at this point), but the front end. There are a lot of
calculations, queries, lots of code,many forms and reports, etc.
Could it use some maintenance to make it more efficient? Absolutely.
Do I have time for that at the moment? Not really. I do what I can
when I can. Yesterday, I did import all the objects into a new
database. That did not solve this particular problem, which is, I can
copy objects (specifically reports) and they open fine, but if I
change the copied report, it will not save or even close.

Because this database is constantly in development (I am the only
developer), I do have my own copy. Otherwise, I would not be able to
make any chanages on it at all.

Also, it doesn't seem to be a corruption of a particular report or
object. This happens on any report. (I wonder if forms are
affected. I don't typically copy those as often and the forms have
been fairly static for awhile (new objects, etc. within the forms, but
no real new forms).

I'm working around this problem now by simply starting with a blank
new report and copying the format from an old report. It works, even
though it is a little more work for me. It's simply weird that this
is happening.

Josetta
On Mar 28, 4:01 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:

Hi, Josetta.

The group works on their own copy.

Unless this means "Each member of the group works with his own copy of the
front end," then it's being shared by more than one user, which is just as
effective as sharing a non-split database.

This is simply a "glitch", I think; one that's
only been happening a few days.

If it's corruption, then it's usually easy to get rid of by creating a new
database file, then importing the objects one group at a time, first the
tables, then the queries, then the forms, et cetera. Once everything is
imported, compile the code, then compact the database and see if you're
still having problems.

How big is the front end, by the way? You called it a monster database, but
the majority of the weight should be in the tables in the back end on the
server.

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.

"Josetta" <[e-mail] in message

news:11**********************@p15g2000hsd.googlegr oups.com...

No, This is not the problem. I have my own development file. It's
open exclusively. The group works on their own copy. There is a
front and back-end. This is simply a "glitch", I think; one that's
only been happening a few days. I routinely make copies of reports
and then edit them according to the new names. Only the past couple
of days has this been a problem.

On Mar 28, 2:53 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:

Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

Do you have the database file open exclusively? If not and other users
are
connected to the front end, design changes can't be saved. If you have
SetWarnings off, you won't receive the warning that the object can't be
saved, IIRC.

It's best to split the database into a back end (tables and
relationships)
and a front end (queries, forms, reports, et cetera), and then place the
back end on the shared network server and place a copy of the front end
on
each user's workstation. For more information on splitting the database,
please see the "Split the Database" tip on the following Web page:

>http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

HTH.
Gunny

Seehttp://www.QBuilt.comforall your database needs.
Seehttp://www.Access.QBuilt.comforMicrosoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com....comhttp://www...
contact
info.

"Josetta" <[e-mail] in message

>news:11**********************@l77g2000hsb.googleg roups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

[engles]

On Mar 28, 2:08 pm, "Josetta" <[e-mail]:

Gunny,

BTW, thank you for your quick replies.

There may be some corruption. The file is huge (typically around 50
megs at this point (compact), but it bloats-- still working on that)
and no, most of the weight is not in the tables (backend is around
25-30 megs at this point), but the front end. There are a lot of
calculations, queries, lots of code,many forms and reports, etc.
Could it use some maintenance to make it more efficient? Absolutely.
Do I have time for that at the moment? Not really. I do what I can
when I can. Yesterday, I did import all the objects into a new
database. That did not solve this particular problem, which is, I can
copy objects (specifically reports) and they open fine, but if I
change the copied report, it will not save or even close.

Because this database is constantly in development (I am the only
developer), I do have my own copy. Otherwise, I would not be able to
make any chanages on it at all.

Also, it doesn't seem to be a corruption of a particular report or
object. This happens on any report. (I wonder if forms are
affected. I don't typically copy those as often and the forms have
been fairly static for awhile (new objects, etc. within the forms, but
no real new forms).

I'm working around this problem now by simply starting with a blank
new report and copying the format from an old report. It works, even
though it is a little more work for me. It's simply weird that this
is happening.

Josetta

On Mar 28, 4:01 pm, "'69 Camaro" <ForwardZERO_SPAM.To.

[e-mail]_SPAMwrote:

Hi, Josetta.

The group works on their own copy.

Unless this means "Each member of the group works with his own copy of the
front end," then it's being shared by more than one user, which is just as
effective as sharing a non-split database.

This is simply a "glitch", I think; one that's
only been happening a few days.

If it's corruption, then it's usually easy to get rid of by creating a new
database file, then importing the objects one group at a time, first the
tables, then the queries, then the forms, et cetera. Once everything is
imported, compile the code, then compact the database and see if you're
still having problems.

How big is the front end, by the way? You called it a monster database, but
the majority of the weight should be in the tables in the back end on the
server.

HTH.
Gunny

Seehttp://www.QBuilt.comforall your database needs.
Seehttp://www.Access.QBuilt.comforMicrosoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com.../www...contact
info.

"Josetta" <[e-mail] in message

news:11**********************@p15g2000hsd.googlegr oups.com...

No, This is not the problem. I have my own development file. It's
open exclusively. The group works on their own copy. There is a
front and back-end. This is simply a "glitch", I think; one that's
only been happening a few days. I routinely make copies of reports
and then edit them according to the new names. Only the past couple
of days has this been a problem.

On Mar 28, 2:53 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:
>Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

>Do you have the database file open exclusively? If not and other users
>are
>connected to the front end, design changes can't be saved. If you have
>SetWarnings off, you won't receive the warning that the object can't be
>saved, IIRC.

>It's best to split the database into a back end (tables and
>relationships)
>and a front end (queries, forms, reports, et cetera), and then place the
>back end on the shared network server and place a copy of the front end
>on
>each user's workstation. For more information on splitting the database,
>please see the "Split the Database" tip on the following Web page:

>>http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

>HTH.
>Gunny

>Seehttp://www.QBuilt.comforallyour database needs.
>Seehttp://www.Access.QBuilt.comforMicrosoftAccess tips and tutorials.
>Blogs:http://www.DataDevilDog.BlogSpot.com....comhttp://www...
>contact
>info.

>"Josetta" <[e-mail] in message

>>news:11**********************@l77g2000hsb.google groups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.- Hide quoted text -

>- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

I can't imagine a 50 MB front-end with no data. I just looked at one
of mine that has 300+ queries (used only for populating forms and
reports, not used in code), 90 forms and subforms, 150 reports and
subreports, with lots of code (I don't use macros) and the whole thing
(including some temporary tables in the front-end) takes just 12
MBytes compacted. Can you do a count of these sorts of things and
compare them to these numbers and see if 50 MB makes sense?

[Tom van Stiphout]

On 28 Mar 2007 14:08:01 -0700, "Josetta" <Jo*****@smartdot.netwrote:

Sounds to me you have a corruption of some kind. You are keeping very
good backups, right?
I would export all objects to text (google for SaveAsText for the
exact syntax), and import them in a new db. What you are seeing is not
normal, and will eventually bite you.

-Tom.

>Gunny,

BTW, thank you for your quick replies.

There may be some corruption. The file is huge (typically around 50
megs at this point (compact), but it bloats-- still working on that)
and no, most of the weight is not in the tables (backend is around
25-30 megs at this point), but the front end. There are a lot of
calculations, queries, lots of code,many forms and reports, etc.
Could it use some maintenance to make it more efficient? Absolutely.
Do I have time for that at the moment? Not really. I do what I can
when I can. Yesterday, I did import all the objects into a new
database. That did not solve this particular problem, which is, I can
copy objects (specifically reports) and they open fine, but if I
change the copied report, it will not save or even close.

Because this database is constantly in development (I am the only
developer), I do have my own copy. Otherwise, I would not be able to
make any chanages on it at all.

Also, it doesn't seem to be a corruption of a particular report or
object. This happens on any report. (I wonder if forms are
affected. I don't typically copy those as often and the forms have
been fairly static for awhile (new objects, etc. within the forms, but
no real new forms).

I'm working around this problem now by simply starting with a blank
new report and copying the format from an old report. It works, even
though it is a little more work for me. It's simply weird that this
is happening.

Josetta
On Mar 28, 4:01 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:

>Hi, Josetta.

The group works on their own copy.

Unless this means "Each member of the group works with his own copy of the
front end," then it's being shared by more than one user, which is just as
effective as sharing a non-split database.

This is simply a "glitch", I think; one that's
only been happening a few days.

If it's corruption, then it's usually easy to get rid of by creating a new
database file, then importing the objects one group at a time, first the
tables, then the queries, then the forms, et cetera. Once everything is
imported, compile the code, then compact the database and see if you're
still having problems.

How big is the front end, by the way? You called it a monster database, but
the majority of the weight should be in the tables in the back end on the
server.

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.

"Josetta" <[e-mail] in message

news:11**********************@p15g2000hsd.googleg roups.com...

No, This is not the problem. I have my own development file. It's
open exclusively. The group works on their own copy. There is a
front and back-end. This is simply a "glitch", I think; one that's
only been happening a few days. I routinely make copies of reports
and then edit them according to the new names. Only the past couple
of days has this been a problem.

On Mar 28, 2:53 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
[e-mail]_SPAMwrote:
Hi, Josetta.

Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

>Do you have the database file open exclusively? If not and other users
are
connected to the front end, design changes can't be saved. If you have
SetWarnings off, you won't receive the warning that the object can't be
saved, IIRC.

>It's best to split the database into a back end (tables and
relationships)
and a front end (queries, forms, reports, et cetera), and then place the
back end on the shared network server and place a copy of the front end
on
each user's workstation. For more information on splitting the database,
please see the "Split the Database" tip on the following Web page:

>>http://www.Access.QBuilt.com/html/ge...1.html#SplitDB

>HTH.
Gunny

>Seehttp://www.QBuilt.comforall your database needs.
Seehttp://www.Access.QBuilt.comforMicrosoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com....comhttp://www...
contact
info.

>"Josetta" <[e-mail] in message

>>news:11**********************@l77g2000hsb.google groups.com...

Access 2003

I've been experiencing some problems with my "monster" database the
last couple of days. I imported all objects into a new database
yesterday, which pretty much stopped the crashing problems, but here's
something weird: Whenever I copy an object (reports so far), I am
able to open it and make changes, but when I try to save it (without
closing), it appears to save (message box goes off), but it doesn't.
Then, if I try to close the report, it doesn't close, doesn't save,
doesn't do anything.

This does not seem to be a problem with a "fresh" report (not copied).

I like to copy and change, because we have a specific "look" to our
reports, which would be a pain to set up each and every time my boss
requests a new report (nearly daily!), plus much of the data stays the
same.

Has anyone else experienced this and is there a cure? I've tried
repairing Access and I compact and compile often. I can't figure out
why this might happen.- Hide quoted text -

>- Show quoted text -- Hide quoted text -

- Show quoted text -