[AccessD] Queries are messed up!

Gary....

You are absolutely right ---  the  "Name Autocorrect" options are the 
culprits --- see
http://alexdyb.blogspot.com/2006/05/user-friendly-name-autocorrect-option.html

Thanks a Bunch!
Barb

----- Original Message ----- 
From: "Gary Kjos" <garykjos at gmail.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Friday, February 09, 2007 10:08 AM
Subject: Re: [AccessD] Queries are messed up!


>A couple of thoughts. First do you have the "Name Autocorrect" options
> checked or unchecked?  I always UNCHECK them so Access doesn't try to
> get to smart when copying tables and queries etc. Second there is an
> option under the Import to "Import Relationships" is that checked?
>
> It sounds like it is treating the imported query as if the table names
> have changed between the versions. Are you sure everything is named
> exactly the same in both versions?
>
> One more thought. And I think this one may be the real answer. If the
> database that you are using doesn't have any table definitions in it,
> perhaps the query there is being compiled somehow and since there are
> no table names it is being confused. You could try including empty
> tables in that bridge database in order to give the query actual
> tables to reference in that temporary database.   Then you just have
> to be sure to not import the empty table definitions into the end
> users database you are intending to update.
>
> Good luck figgering it out.
>
> GK
>
> On 2/8/07, Barbara Ryan <BarbaraRyan at cox.net> wrote:
>> In an Access 2002 application, when I need to distribute database object
>> changes, I copy all of the modified objects into a blank database and
>> email it to client sites.  They then click a push button in their
>> application which imports all of the objects.
>>
>> Everything has worked great (for years) until now ---- if a query is
>> included in the update, it will import into their application without any
>> relationships (i.e., there are no "lines" between tables) when the query
>> is viewed in design mode on their computer.  Also, even if the query only
>> contains one table, all of the selected fields are listed as "Exp1", etc.
>> For example, what used to appear as "EmpNo" now displays as
>> "Expr1:EmpNo".
>>
>> I have duplicated this problem myself by importing the objects into
>> another database on my computer.
>>
>> We (the clients and I) have recently upgraded to Access 2003.
>>
>> Any ideas?  Or should I call Ghostbusters again :-(
>>
>> Thanks,
>> Barb Ryan
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>
>
> -- 
> Gary Kjos
> garykjos at gmail.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com