PC Review


Reply
Thread Tools Rate Thread

database strange behavior

 
 
Alain
Guest
Posts: n/a
 
      7th Jun 2010
I do not know if it was already posted !!!
Hi to all,

I am wondering if some of you MVP can shed some light on this strange
behavior.
I have develop a database FE/BE and trnasfer old data from a legacy Access97
db. Everything was working just fine until this past monday.
I am starting getting error 3044 ... wrong file path msg from user,the path
in the msg was pointing directly to my development folder on my desktop.
I found out which table was causing the problem, so I just rebuild it,
transfer data fom the problem table to the new one, ran test and get the same
error, this time I decide to create again a new table, but this time directly
on the BE db sitting on the network, worked fine for 2 days.

Now, the fun part, I needed to add another control to the main form, write
about a dozen line of code for it and that is it.
To test this control, I make a copy of the BE db to my machine for testing
purpose with the latest data, (FYI; I never use the real one, always copies)
ran test and everythig is fine. I release the updated version on the network
so the users can start using it.
The next day, when the user ( different one ) is opening the new version, he
is getting the same error again, but this time, not only with 1 tables but
with 7 different ones this time. (the original problem table is included in
the 7, I just ran thru my code to relink manually to find out which is
causing problems).
I have absolutly no idea why all of sudden I am getting these bunch of 3044
errors, the BE is always at the same location on the network.
My BE db contains approx 160 tables and the process is always the same, When
the user start the program, it is checking to see if there is a newer version
available, if not then it continues with the same program.
If a new version is avalaible, it shuts down automatically so the end user
must use the newer version, once that process is done,
then the program start checking all linked tables and refreshes them and
then problems starts....

At one point in time I was not even able to manually relink the tables so
they can keep working until I find out what is the real problem behind this.

So what I did is I transfer all my forms, reports, modules, queries to a
blank db, compile an release it, same problem again when trying to connect,
so I did transfer all tables to a blank one, compact and repair and try
again, same problem, try to link manually, was not albe because of the same
problem.

the only solution for the time being is to put everything together into 1
new single db and run the program from the network, not the best but at least
I do not get those errors. We are currently using Access 2007 on XP machines.

So my question is what can possibly cause this "all of a sudden" strange
behavior ? How can I resolve this ?
I have tried averything I possibly know but I still hit the wall....
Iam open to anything, any discussion that will help me out on this one.




 
Reply With Quote
 
 
 
 
Tom van Stiphout
Guest
Posts: n/a
 
      9th Jun 2010
On Mon, 7 Jun 2010 07:25:01 -0700, Alain
<(E-Mail Removed)> wrote:

This is hard to trouble-shoot without actually being onsite.
Perhaps you are using mapped drives to link to the BE, and different
people have them mapped different ways?
Perhaps your reattach code is not as robust as you thought?

-Tom.
Microsoft Access MVP


>I do not know if it was already posted !!!
>Hi to all,
>
>I am wondering if some of you MVP can shed some light on this strange
>behavior.
>I have develop a database FE/BE and trnasfer old data from a legacy Access97
>db. Everything was working just fine until this past monday.
>I am starting getting error 3044 ... wrong file path msg from user,the path
>in the msg was pointing directly to my development folder on my desktop.
>I found out which table was causing the problem, so I just rebuild it,
>transfer data fom the problem table to the new one, ran test and get the same
>error, this time I decide to create again a new table, but this time directly
>on the BE db sitting on the network, worked fine for 2 days.
>
>Now, the fun part, I needed to add another control to the main form, write
>about a dozen line of code for it and that is it.
>To test this control, I make a copy of the BE db to my machine for testing
>purpose with the latest data, (FYI; I never use the real one, always copies)
>ran test and everythig is fine. I release the updated version on the network
>so the users can start using it.
>The next day, when the user ( different one ) is opening the new version, he
>is getting the same error again, but this time, not only with 1 tables but
>with 7 different ones this time. (the original problem table is included in
>the 7, I just ran thru my code to relink manually to find out which is
>causing problems).
>I have absolutly no idea why all of sudden I am getting these bunch of 3044
>errors, the BE is always at the same location on the network.
>My BE db contains approx 160 tables and the process is always the same, When
>the user start the program, it is checking to see if there is a newer version
>available, if not then it continues with the same program.
>If a new version is avalaible, it shuts down automatically so the end user
>must use the newer version, once that process is done,
>then the program start checking all linked tables and refreshes them and
>then problems starts....
>
>At one point in time I was not even able to manually relink the tables so
>they can keep working until I find out what is the real problem behind this.
>
>So what I did is I transfer all my forms, reports, modules, queries to a
>blank db, compile an release it, same problem again when trying to connect,
>so I did transfer all tables to a blank one, compact and repair and try
>again, same problem, try to link manually, was not albe because of the same
>problem.
>
>the only solution for the time being is to put everything together into 1
>new single db and run the program from the network, not the best but at least
>I do not get those errors. We are currently using Access 2007 on XP machines.
>
>So my question is what can possibly cause this "all of a sudden" strange
>behavior ? How can I resolve this ?
>I have tried averything I possibly know but I still hit the wall....
>Iam open to anything, any discussion that will help me out on this one.
>
>
>
>

 
Reply With Quote
 
Jeff Boyce
Guest
Posts: n/a
 
      9th Jun 2010
I'm with Tom ... hard to diagnose without more information.

Is there a chance that you are using "sharenames" for the path to the
backend tables, rather than UNC-named paths? If so, there's no guarantee
that the "N:" drive you set up on your PC is the same mapping that someone
else used for their "N:" (or that they even have one!).

And just to confirm, because you may be using the terms differently than I
do ... do you have a single copy of the back-end (i.e., the tables only) on
a server someplace on your local area network, and a copy of the front-end
on each/every user's PC?

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Alain" <(E-Mail Removed)> wrote in message
news:0DF9DAE4-BE40-4C1A-A468-(E-Mail Removed)...
>I do not know if it was already posted !!!
> Hi to all,
>
> I am wondering if some of you MVP can shed some light on this strange
> behavior.
> I have develop a database FE/BE and trnasfer old data from a legacy
> Access97
> db. Everything was working just fine until this past monday.
> I am starting getting error 3044 ... wrong file path msg from user,the
> path
> in the msg was pointing directly to my development folder on my desktop.
> I found out which table was causing the problem, so I just rebuild it,
> transfer data fom the problem table to the new one, ran test and get the
> same
> error, this time I decide to create again a new table, but this time
> directly
> on the BE db sitting on the network, worked fine for 2 days.
>
> Now, the fun part, I needed to add another control to the main form, write
> about a dozen line of code for it and that is it.
> To test this control, I make a copy of the BE db to my machine for testing
> purpose with the latest data, (FYI; I never use the real one, always
> copies)
> ran test and everythig is fine. I release the updated version on the
> network
> so the users can start using it.
> The next day, when the user ( different one ) is opening the new version,
> he
> is getting the same error again, but this time, not only with 1 tables but
> with 7 different ones this time. (the original problem table is included
> in
> the 7, I just ran thru my code to relink manually to find out which is
> causing problems).
> I have absolutly no idea why all of sudden I am getting these bunch of
> 3044
> errors, the BE is always at the same location on the network.
> My BE db contains approx 160 tables and the process is always the same,
> When
> the user start the program, it is checking to see if there is a newer
> version
> available, if not then it continues with the same program.
> If a new version is avalaible, it shuts down automatically so the end user
> must use the newer version, once that process is done,
> then the program start checking all linked tables and refreshes them and
> then problems starts....
>
> At one point in time I was not even able to manually relink the tables so
> they can keep working until I find out what is the real problem behind
> this.
>
> So what I did is I transfer all my forms, reports, modules, queries to a
> blank db, compile an release it, same problem again when trying to
> connect,
> so I did transfer all tables to a blank one, compact and repair and try
> again, same problem, try to link manually, was not albe because of the
> same
> problem.
>
> the only solution for the time being is to put everything together into 1
> new single db and run the program from the network, not the best but at
> least
> I do not get those errors. We are currently using Access 2007 on XP
> machines.
>
> So my question is what can possibly cause this "all of a sudden" strange
> behavior ? How can I resolve this ?
> I have tried averything I possibly know but I still hit the wall....
> Iam open to anything, any discussion that will help me out on this one.
>
>
>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Need Help: Strange, Strange Behavior ( Not Me. My Model! ) SteveM Microsoft Excel Programming 2 16th Dec 2007 06:02 PM
Strange IE Behavior Tony Windows XP Internet Explorer 8 31st Jul 2005 05:31 PM
VERY Strange behavior! =?Utf-8?B?U2NyYXRjaGluZyBteSBIZWFk?= Windows XP General 7 14th Jan 2005 08:06 AM
strange behavior Bob Britton Microsoft Windows 2000 1 12th Nov 2004 07:01 PM
Strange behavior Anita Gupta Microsoft Outlook Form Programming 0 7th Jan 2004 07:35 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 07:49 AM.