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

Strange Problems - Which parts are my fault? (A2K database)

P: n/a
Very strange behavior, but I suspect some is A2K and some might be for
me to correct. Just trying to see if anyone can help and advise.

We have a database that's been running for a few years with no
problems. We continuously add queries and reports. We're up to about
700 queries (no, not all are used and most are parameter queries - the
business asks a LOT of questions!), and under 250 reports and fewer
than 15 forms.

Data is largely sent to us from an outside vendor and we store it (in a
backend) and write queries and reports against it (front end).

It is all in one big front-end and all of a sudden the "Sales tax"
calculations won't work and is causing bizarre behavior.

First step was to create a new db and import all the objects. Now, the
questions:
1. We could "select all" and import all the queries - it was FAST!!
2. We could NOT "select all" and import all the reports. Had to split
into loads of separate selections.
We do have a lot of cross tab queries - could that be why?
We have something that "appeared" at the top of the list of reports
(never saw it before) and ended up in the new db (didn't select it) -
~TMPCLP87011. Any idea what this is? I looked at an old backup and it
was there, and the database was working then.

Still not working.

The "Sales Tax" process uses 22 cross-tab queries to create a table of
data for the next queries and reports. It's been working, but runs a
long time. I suspect there's a better way, which I'm brainstorming now
and asking for help. Could that be the problem?

Loads of questions; just don't know where to go to fix this. Taxes are
due next week, so we have to figure something out.

Thanks!
sara

Jan 5 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a

sara wrote:
Very strange behavior, but I suspect some is A2K and some might be for
me to correct. Just trying to see if anyone can help and advise.

We have a database that's been running for a few years with no
problems. We continuously add queries and reports. We're up to about
700 queries (no, not all are used and most are parameter queries - the
business asks a LOT of questions!), and under 250 reports and fewer
than 15 forms.

Data is largely sent to us from an outside vendor and we store it (in a
backend) and write queries and reports against it (front end).

It is all in one big front-end and all of a sudden the "Sales tax"
calculations won't work and is causing bizarre behavior.
What bizarre behavior?
First step was to create a new db and import all the objects. Now, the
questions:
1. We could "select all" and import all the queries - it was FAST!!
2. We could NOT "select all" and import all the reports. Had to split
into loads of separate selections.
What happened when you tried to import all the reports?

Have you tried decompiling and repairing (front and back end) first?

Bruce

Jan 5 '07 #2

P: n/a
Will try decompile/recomplie. Didn't think of that one. Did several
compact and repair.

We got all the reports in and it seems to work on everything we've
needed except taxes. Also, that weird ~file/thing is in the reports
list if we use the new db as a source for "import", even tho we didn't
select it for import from the original db.

"You cannot run this action at the present time" is the message we get
after decompile/recompile.

Sara
de***************@gmail.com wrote:
sara wrote:
Very strange behavior, but I suspect some is A2K and some might be for
me to correct. Just trying to see if anyone can help and advise.

We have a database that's been running for a few years with no
problems. We continuously add queries and reports. We're up to about
700 queries (no, not all are used and most are parameter queries - the
business asks a LOT of questions!), and under 250 reports and fewer
than 15 forms.

Data is largely sent to us from an outside vendor and we store it (in a
backend) and write queries and reports against it (front end).

It is all in one big front-end and all of a sudden the "Sales tax"
calculations won't work and is causing bizarre behavior.

What bizarre behavior?
First step was to create a new db and import all the objects. Now, the
questions:
1. We could "select all" and import all the queries - it was FAST!!
2. We could NOT "select all" and import all the reports. Had to split
into loads of separate selections.

What happened when you tried to import all the reports?

Have you tried decompiling and repairing (front and back end) first?

Bruce
Jan 5 '07 #3

P: n/a

sara wrote:
Will try decompile/recomplie. Didn't think of that one. Did several
compact and repair.

We got all the reports in and it seems to work on everything we've
needed except taxes. Also, that weird ~file/thing is in the reports
list if we use the new db as a source for "import", even tho we didn't
select it for import from the original db.

"You cannot run this action at the present time" is the message we get
after decompile/recompile.

Sara
de***************@gmail.com wrote:
sara wrote:
Very strange behavior, but I suspect some is A2K and some might be for
me to correct. Just trying to see if anyone can help and advise.
>
We have a database that's been running for a few years with no
problems. We continuously add queries and reports. We're up to about
700 queries (no, not all are used and most are parameter queries - the
business asks a LOT of questions!), and under 250 reports and fewer
than 15 forms.
>
Data is largely sent to us from an outside vendor and we store it (in a
backend) and write queries and reports against it (front end).
>
It is all in one big front-end and all of a sudden the "Sales tax"
calculations won't work and is causing bizarre behavior.
What bizarre behavior?
First step was to create a new db and import all the objects. Now, the
questions:
1. We could "select all" and import all the queries - it was FAST!!
2. We could NOT "select all" and import all the reports. Had to split
into loads of separate selections.
What happened when you tried to import all the reports?

Have you tried decompiling and repairing (front and back end) first?

Bruce
You never did state what the 'bizarre behavior' was. Is there an error
message? Maybe you just got some new data that falls outside the
bounds of what your queries expect. If not then perhaps there is
corruption in the back end database. I would try creating a new back
end and importing the tables into it. Then compact and repair the new
back end. Once you've got a clean back end I'd create a new front end
and link to the tables in the back end. Then I'd import the non-table
objects from the old front end to the new one. You may find that it is
speedier to debug the whole process if you temporarily put all of the
objects in one database on a local workstation. Then when you get it
all working you can split it back out into two parts.

Bruce

Jan 8 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.