Gary Kjos
garykjos at gmail.com
Fri Feb 15 13:04:07 CST 2013
Hi Ed, I think I can help with your first issue but not the second one.... You want to go into Tools / Options and then to teh Tables/Queries tab and clear out everyting from the "AutoIndex on Import/Create" box. These are field prefixes or suffixes that it will try to make indexes on on imports or new table creations. An explanation with screen grabs is here... http://www.fmsinc.com/free/newtips/access/AutoIndex/index.asp GK On Fri, Feb 15, 2013 at 12:33 PM, Edward Zuris <edzedz at comcast.net> wrote: > > > Hello: Database Advisors, > > > > I have a couple of issues that wondering if anyone has come across. > > > > I am using Access-2003 32-bit. > > > > 1). > > > > The first is a field called 'Roomkey'. When I import that table > > into another Ms-Access database that field becomes a 'KEY-Field'. > > > > The 'Roomkey' field describes the type of key for a hotel room > > which doesn't need to be a key field. > > > > That is a problem because all the numbers of indexes are used up > > and that extra key upsets the import process. > > > > Is there a way to turn that feature off ? > > > > 2). > > > > The second issue is when in Windows-7 Pro, Ms-Access doesn't seem > > to behave the same as when using XP Pro. Especially when it comes > > to speed. > > > > The only way to have Ms-Access behave the same with comparable > > speed is to get into Windows-7 Pro task-manager and change the > > msaccess.exe job to RealTime priority. > > > > Since the machine is a dual process computer, this doesn't seem > > to cause other problems. > > > > So, is there a way to have the msaccess.exe job just start up using > > the RealTime priority ? > > > > Thanks. > > > > Sincerely, > > Ed Zuris. > > edzedz at comcast.net > > > > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- Gary Kjos garykjos at gmail.com