Question about Microsoft Computers & Internet

1 Answer

Upgrading from 2003 access database to 2007

I have microsoft office 2007, I would like to update my 2003 Access database to 2007. I have 3 front users and the back end is stored on the server. Could you give me fairly user friendly instructions to do this please. I am not terribly confident with this. Also can you tell me how to unlink tables please

Posted by on

1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    Hot-Shot:

    An expert who has answered 20 questions.

    Corporal:

    An expert that hasĀ over 10 points.

    Mayor:

    An expert whose answer gotĀ voted for 2 times.

  • Expert
  • 73 Answers

I would leave your database as Access 2003. the 2007 version has many bugs and will give you many more problems than its worth. Access 2003 is very stable, you should be able to keep it at that for many years.

Posted on Feb 07, 2009

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Recently I had replaced one of HDD of my DL580 service Raid 5 configuration. After that everything working fine including user connectivity and database access. My question is both the LEDs on replace


After you replaced the drive, did you rebuild the RAID array? Some of the higher end RAID controllers will try to rebuild automatically (if set to do so) but most must be rebuilt manually.

Dec 22, 2014 | HP ProLiant DL580 G5 (438087-001) Server

Tip

Understanding windows account lockups


Common Causes for Account Lockouts

This section describes some of the common causes for account lockouts The common troubleshooting steps and resolutions for account lockouts are also described in this section.

To avoid false lockouts, check each computer on which a lockout occurred for the following behaviors:

* Programs: Many programs cache credentials or keep active threads that retain the credentials after a user changes their password.

* Service accounts: Service account passwords are cached by the service control manager on member computers that use the account as well as domain controllers. If you reset the password for a service account and you do not reset the password in the service control manager, account lockouts for the service account occur. This is because the computers that use this account typically retry logon authentication by using the previous password. To determine whether this is occurring, look for a pattern in the Netlogon log files and in the event log files on member computers. You can then configure the service control manager to use the new password and avoid future account lockouts.

* Bad Password Threshold is set too low: This is one of the most common misconfiguration issues. Many companies set the Bad Password Threshold registry value to a value lower than the default value of 10. If you set this value too low, false lockouts occur when programs automatically retry passwords that are not valid. Microsoft recommends that you leave this value at its default value of 10. For more information, see "Choosing Account Lockout Settings for Your Deployment" in this document.

* User logging on to multiple computers: A user may log onto multiple computers at one time. Programs that are running on those computers may access network resources with the user credentials of that user who is currently logged on. If the user changes their password on one of the computers, programs that are running on the other computers may continue to use the original password. Because those programs authenticate when they request access to network resources, the old password continues to be used and the users account becomes locked out. To ensure that this behavior does not occur, users should log off of all computers, change the password from a single location, and then log off and back on.

noteNote
Computers running Windows XP or a member of the Windows Server 2003 family automatically detect when the users password has changed and prompt the user to lock and unlock the computer to obtain the current password. No logon and logoff is required for users using these computers.

* Stored user names and passwords retain redundant credentials: If any of the saved credentials are the same as the logon credential, you should delete those credentials. The credentials are redundant because Windows tries the logon credentials when explicit credentials are not found. To delete logon credentials, use the Stored User Names and Passwords tool. For more information about Stored User Names and Passwords, see online help in Windows XP and the Windows Server 2003 family.

noteNote
Computers that are running Windows 95, Windows 98, or Windows Millennium Edition do not have a Stored User Names and Passwords file. Instead, you should delete the user's .pwl file. This file is named Username.pwl, where Username is the user's logon name. The file is stored in the Systemroot folder.

* Scheduled tasks: Scheduled processes may be configured to using credentials that have expired.

* Persistent drive mappings: Persistent drives may have been established with credentials that subsequently expired. If the user types explicit credentials when they try to connect to a share, the credential is not persistent unless it is explicitly saved by Stored User Names and Passwords. Every time that the user logs off the network, logs on to the network, or restarts the computer, the authentication attempt fails when Windows attempts to restore the connection because there are no stored credentials. To avoid this behavior, configure net use so that is does not make persistent connections. To do this, at a command prompt, type net use /persistent:no. Alternately, to ensure current credentials are used for persistent drives, disconnect and reconnect the persistent drive.

* Active Directory replication: User properties must replicate between domain controllers to ensure that account lockout information is processed properly. You should verify that proper Active Directory replication is occurring.

* Disconnected Terminal Server sessions: Disconnected Terminal Server sessions may be running a process that accesses network resources with outdated authentication information. A disconnected session can have the same effect as a user with multiple interactive logons and cause account lockout by using the outdated credentials. The only difference between a disconnected session and a user who is logged onto multiple computers is that the source of the lockout comes from a single computer that is running Terminal Services.

* Service accounts: By default, most computer services are configured to start in the security context of the Local System account. However, you can manually configure a service to use a specific user account and password. If you configure a service to start with a specific user account and that accounts password is changed, the service logon property must be updated with the new password or that service may lock out the account.

noteNote
You can use the System Information tool to create a list of services and the accounts that were used to start them. To start the System Information tool, click Start, click Run, type winmsd, and then click OK.

Other Potential Issues

Some additional considerations regarding account lockout are described in the following sections.
Account Lockout for Remote Connections

The account lockout feature that is discussed in this paper is independent of the account lockout feature for remote connections, such as in the Routing and Remote Access service and Microsoft Internet Information Services (IIS). These services and programs may provide their own unrelated account lockout features.
Internet Information Services

By default, IIS uses a token-caching mechanism that locally caches user account authentication information. If lockouts are limited to users who try to gain access to Exchange mailboxes through Outlook Web Access and IIS, you can resolve the lockout by resetting the IIS token cache. For more information, see "Mailbox Access via OWA Depends on IIS Token Cache" in the Microsoft Knowledge Base.
MSN Messenger and Microsoft Outlook

If a user changes their domain password through Microsoft Outlook and the computer is running MSN Messenger, the client may become locked out.

In this case, since the user has multiple devices connected to the exchange at given time , if he changes the password without disconnecting the other deivices. The account would get locked. You can inform him disconnect all the devices from the exchange except for one machine to change the paswword and then reconnect other devices with new creditentials.


Thanks
Proton

on May 29, 2010 | Computers & Internet

1 Answer

I can access any profiles


Please login with Administrator, then add your user in administrators group, Login with your user and then try to access your profile. It would work.

Regards,
Kaushik Patel

Sep 03, 2013 | Computers & Internet

1 Answer

Ufs update


Check with your SYSTEM ADMINISTRATOR... for possible PASSWORD LOGIN CHANGE or for admin. configuration(s) changes

Jun 14, 2013 | Computers & Internet

1 Answer

We have Server 2003 set up at our clients office. We use RDP to access them remotely for out staff to work. The problem is 1-2 times a week when we come try to connect on the morning, you cannot? The only...


I assume you checked the obvious...
Firewall rules, Port Forwarding, services...

A while back there was an issue related to video drivers on some systems creating symptoms like that. If you have either an ATI or a nVidia graphic card/driver installed, try to update the drivers or roll back to an earlier version to check if that resolves the issue.

Let me know how it goes or if you have to dig further.

Dec 20, 2012 | Computers & Internet

2 Answers

Differences between 2003 server and 2008 server


The main difference between 2003 and 2008 is Virtualization, management.

2008 has more inbuild components and updated third party drivers.

Note: Windows server 2008 45 time fast compare to win 2003.

In Windows Server 2008, Microsoft is introducing new features and technologies, some of which were not available in Windows Server 2003 with Service Pack 1 (SP1), that will help to reduce the power consumption of server and client operating systems, minimize environmental byproducts, and increase server efficiency.
Microsoft Windows Server 2008 has been designed with energy efficiency in mind, to provide customers with ready and convenient access to a number of new power-saving features. It includes updated support for Advanced Configuration and Power Interface (ACPI) processor power management (PPM) features, including support for processor performance states (P-states) and processor idle sleep states on multiprocessor systems. These features simplify power management in Windows Server 2008 (WS08) and can be managed easily across servers and clients using Group Policies.
Windows Server 2008 introduces Hyper-V (V for Virtualization) but only on 64bit versions. More and more companies are seeing this as a way of reducing hardware costs by running several 'virtual' servers on one physical machine. If you like this exciting technology, make sure that you buy an edition of Windows Server 2008 that includes Hyper-V, then launch the Server Manger, add Roles.

Windows Server 2008, formerly codenamed Longhorn, is no leas than 45 times faster than its predecessor, Windows Server 2003, in terms of network transfer speeds. Now whatever the perspective is on Microsoft's last 32-bit server operating system, the fact of the matter is that faster transfer speeds for of up to 45 times is quite an evolution compared to Windows Server 2003. Back in June 2007, Microsoft commissioned a study to the Tolly Group focused on the networking performances of its latest Windows client and server operating system, which ended up as the "Enhanced Network Performance with Microsoft Windows Vista and Windows Server 2008" whitepaper. The paper pointed to the fact that both Vista and Windows Server 2008 managed to offer "Dramatic network performance benefits".


Read more: What is the difference between server 2003 and 2008 in the functions and services? ' Answerbag http://www.answerbag.com/q_view/559903#ixzz18uM0qGWP you can read more http://wiki.answers.com/Q/What_are_the_differences_between_Windows_Server_2003_and_Windows_Server_2008

Hope this helps. Please rate my response.
Thanks.
Have a good day

Dec 23, 2010 | Microsoft Computers & Internet

1 Answer

I am getting a error code of 1304. wants to verify if i have access to that directory


If you tried to access the BCD file and got the error. Then follow the steps in the below microsoft article

http://technet.microsoft.com/en-us/library/cc726613(WS.10).aspx

Oct 20, 2009 | HP Computers & Internet

1 Answer

Compaq ProLiant ML370 G3


Hello,

How big if your environment? How many users? Do you have remote access needs? If your environment is under 75 users then you might want to consider moving to Windows Small Business Server. It's a great little package that includes Exchange with it. You can also get the premium edition which includes Sharepoint.

Don't forget licensing needs during this whole process too. You want to make sure you are covered properly with software licenses from Microsoft when making the migration.

The hardware specs seem adequate but it will depend on the amount of users in your environment and workload for it.

I've included three links to different options for migration:

This link is pretty good to explain using the Microsoft tool.

http://www.petri.co.il/active_directory_migration_tool_usage_w2k_windows_2003.htm

This link provides info on the swing migration which is a bit more popular in the small business arena. Works pretty good. I've done it a few times.
http://www.sbsmigration.com/pages/14/

This link is for Acronis products that allow for easy ghosting or copying of data from one server to another. The good thing about this tool is that your SIDs are kept the same. So I don't know if its a big deal (depends on your environment size) but it can be a pain to rejoin workstations to a domain if new servers are added without successfully moving necessary settings. I've used this tool a few times. It's quick and easy.
http://www.acronis.com/enterprise/products/ATISWin/

I look forward to hearing more from you. Please update me on the questions I asked and if I can help further I will be glad too. Don't forget to rate the solutions once we're done! Thanks.

Mar 28, 2009 | HP Compaq ProLiant ML370 G3 Server

3 Answers

Access 2000 database won't compact and repair.


mchampion,

You are in luck. I had the same problem a while back. Most of the time you will not be able to compact and repair a database that has reached capacity, however, you can import the database into a new one. The first thing you are going to have to do is find a very large table in your database and copy it into a new one. Then, delete that table from your old database. Now, open another new database. Go to the file menu and choose import. Now you must find your database in the directory and click it. Now choose one of the given options (tables, queries, etc.). Then, Press control + a to select all items. Now hit okay and it will import all of the items from your old database from that section into the new one. You must do this for each section (tables, queries, etc.). When everything is imported (should take less than an hour), compact and repar the new database. This will give you additional space to work with. Now you can bring in the table that you copied into a new database earlier the same way (import). This should put you back in business.
I suggest creating a 2nd database for any other data you may want to add later. You can always make link tables and such in your old database in order to get the additional data and prevent crashing your old database.
Let me know if you need any additional help.

ArthurB

Apr 24, 2008 | Computers & Internet

Not finding what you are looking for?
Computers & Internet Logo

Related Topics:

84 people viewed this question

Ask a Question

Usually answered in minutes!

Top Microsoft Computers & Internet Experts

micky dee

Level 3 Expert

2635 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18330 Answers

Prashant M
Prashant M

Level 3 Expert

2259 Answers

Are you a Microsoft Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...