I used the Get External Data/Import wizard to import an Excel spreadsheet. When the wizard asked about the primary key, I chose "I will chose the primary key" and chose Employee Id.
I then imported successfully. all the fields and records are correct. However, when I go to add see if the primary key is in the Design view, it's not. I try to add the primary key to the Employee ID field and get the messg:
Index or primary key cannot contain null value.
I did a compact & repair and tried again. Can someone tell me why I get this message and how to fix it? Thanks.
I have spent many nights and days on this forum, learning about Access. With the community help, examples and problems solved, I finally managed to complete a Database that runs a charity stock control and sales function.
Currently it is used by 3 users over a network. A central PC hosts it on a Fileshare (as an .mdb file) and the others connect to it via shortcuts to mapped a drive (W; is mapped to the host PC fileshare)
All worked well.
A new XP Pro PC was put in place as the Host PC. Setup was mirrored and worked fine for 2 days. On the 3rd Day the user put a password on the XP profile to secure the PC, and the database began to misbehave only on the New host PC. The other PC are still working fine.
I am unable to run any reports (some have VB in for .has no data). I am unable to run one of the core scheduling forms which uses Allen Brownes excellent Calendar (the one with the highlighter). But the strange thing is that I cannot even enter design mode on the form. Just does nothing, no errors, no prompts.
Copied database to another PC and it all runs fine. Problem is isolated to this new PC. Checked VB references, ran Office updates to SP2, but still no difference.
Would anybody have any suggestions for a way forward??
PS, Thanks to all moderators and experts for excellent work on this forum.
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
I have created a very simple Access database with a CompaniesTbl, ContactsTbl and CallsTbl. The database is used to record telesales contact with customers. The tables are set up like this:
The CompaniesTbl has an AutoNumber Primary Key field called CompanyID.
The ContactsTbl has an AutoNumber Primary Key field called ContactID and a foreign key called CompanyID.
The CallsTbl has an AutoNumber Primary Key field called CallID and foreign key called ContactID.
The relationships are set up in the relationships window and referential integrity imposed.
Twice now, while editing a contact record, an error has occured. Task Manager has had to be used to get out of it. The error is either a 'run-time error with a message that does not mean anything' or it says 'unrecognized database format' (!?).
If you open the database again the ContactID field in the Contacts Table is no longer a Primary Key field. If you look in the relationships window - the relationship between the Companies and Contacts tables no longer exists.
I had converted a Access (shared) DB from 97 to 2000. Now when more then one person open it it tells the others that it has been opened in an admin state denying the other users the ability to open. I checked the options and toggled back and forth to exclusive and back to shared, with no luck. Any ideas?
I just got a new machine with office 2003 but it doesn't include ms access. Can I use access2k with this new version of office?? so I can do reports and put them into word etc??
I created a db in access 97. It has tabkes, queries, forms, modules and reports Now i am trying to convert it into access 2000 but .... thats why i am here.
Here is what i am doing: 1- open access 2000 2- go to tools, db utilities, convert db to 2002 3- select the access 97 db
After that access 2000 starts to make the convertion and at the end it display an error like:
"Microsoft Access has encountered a problem and needs to close. we are sorry for the inconvenience."
Also gives me the option to repair the db and restart access.
At the moment the company Im with uses Access 2000, however ive been told by a few people that Access 2000 had alot of issues and it would be worth informing the company to upgrade to 2003 asap. Is there any major concerns with 2000? Some of the databases currently being used are very large and complex. Any chance data could be lost/displayed incorrectly? etc
:confused:I have created a small DB to keep track of meetings. Main Form customer Sub form meetings with customer At the end of each meeting I make notes on the sub form and enter an agreed date for next meeting. Q 1. I would like the sub form to open at new record, or last record and with the agreed meeting date CARRIED OVER to the new record form. Have unsuccessfully tried (among many) DoCmd.GoToRecord , , acNewRec Q 2 I love the idea of having a sub form, but am unsure when creating reports how to ask for information from “last record”.
thanks have spent hours looking thru messages and closest I found was Dmax but not sure how or where to find/use this.
I'm new to MS Access. I want to know about compressed/reindexed databases.
What happens when a database is compressed? What happens when a database is reindexed? Why is it important to periodically compress and reindex a database?
I have records in the database that I need to pull up by local time zones, what would be the most effective way to do this?
I have a form that submits to an access database which has auto number enabled.. Trouble is that some of the submissions are missing and the database skips an ID number.
I need to develop an application that works in 2002. I tried to take a 2002 mdb, convert in 2002 to 2000 and try it on my machine at home. It didn't work and I couldn't find the missing reference. I then took an mdb that was originally a 2000 format, converted it to 2002 and it worked fine. So what I want to do is develop the app in 2000 and just convert it over to 2002. This allows me to work on it from home which is pretty important since my deadline is creeping closer. Am I ok doing this or am I courting disaster? Or is there another way of doing this?
Is there a way in Access 2000 that I can set up a users table? Basic info:
Name Phone Number Fax Number
Then every time the database is opened they are prompted for their name?
I have a database that has a Fax Cover Sheet within the DB, when they click the Fax Cover Sheet Form I want their information to automatically be generated into the form based on the information from the original table.
How unusual is it for a database to become MUCH smaller when converting it from 2000 to 2003 formats. I mean 600megs to 10 megs. And as far as I can tell all the records are intact....!
I have a rather large project that has been developed in Access 2000. Generally all my distributions have been to PC's with Access available. However, I do find that there are a few that don't. Obviously this is where Run time would be useful. Having never used it I have a few questions if someone could possibly help:-
1 If I have a program developed in Access 2k can it be converted to the MOD version to include runtime? 2 If there is a conversion process is it automatic or does it require extensive reworking of the project? 3 Is it still possible to purchase MOD 2000 or do I need to get an updated version and if so will that still work with Office 2k?
How do I copy the results of a query to a new table that serves as an archive? How can I then clear or reset the original query?
I am doing a project that records the names of students who have had more than 5 merits in school. I want to use this data to generate a certificate to give out at assembly and to send a letter home. I have run a count query but want to send the results to another table which acts as an archive. I want to have the original query reset. Can anybody give me any suggestions?
We are a school operating around 160 computers with Microsoft Office 2000 fully installed on all of them. There have been problems with Microsoft Access in one particular room where students frequently lose their Microsoft Access Reports as a result of clicking on Print, which is then followed by the following message:
Msaccess.exe - Application Error : The instruction at "0x77fcd79a" referenced memory at "0x00000000". The memory could not be "written".
This problem occurs when the students try to print their MSAccess Reports.
The computers in the entire school all have Windows 2000, latest service packs, patches, hotfixes and service packs for Office 2000, but for a reason we can't identify this only happens in one room. It is connected to a QMS Magicolor 2350.
We have just sold our first database which is written in Access 2000. However the buyer runs 2003 and we are having trouble with getting it to run correctly. Does anyone know anything about programming differences between MS 2000 Access and 2003?
Also is it possible to install both 2000 and 2003 on one computer (and also 2007)?
So far our problems are: 1. We are tripping their security alerts. 2. We can't seem to read public variables from another form.
I've got a fairly complex access 2000 database that's split into front and back ends.
There's 32 back end tables and a whole host of complex front end queries and forms. The whole thing's around 25,000 lines of code so not a 5 minute job to rebuild! (sorry but i just can't stop tweaking it!!)
I hate the idea of all that data moving across the network, and having to make the front end machines work so hard so I'd like to get the server doing it's fair share of work because it's got dual 3Ghz Xeon processors which aren't earning their keep! I was thinking about converting the mdb to SQL and although i could pay someone to do it for me, i do like to learn! (so when it breaks i'm not at anyone's mercy!!)
I assume there isn't an upsizing tool on the planet that will let me do this by clicking a button so can anyone point me in the right direction with regard to something decent that can automate as much as possible. PLUS a good source of information on the differentces between access and SQL so that i can start seeing how to accomplish with SQL what i'd do in Access?
