MS Access - SQL View. Select the Query Design from the Create tab and add the tblEmployees table. Select the field you want to see as query result and then run your query. You can now see all the employee information as query result. You have selected certain fields in the Query Grid; at the same time.
Hi all
I have a table in access that I want to update from another table that I have imported from excel.
The imported table contains updated information relating to the records in the current access table. How do I...
'lookup the records in the current table, and if information in the imported table exists (and therefore is either updated information, or is exactly the same information as what's already in the curent table) update the records in the current table'.
I also want any new records to be added to the current table.
I thought I'd do this my using an 'update query', but I think I took this query to mean something else.
A unique ID do not exist in either table (a design flaw I have inheritted and I cannot introduce one for records coming from the import table). Also, each record has a user number, but a user (and therefore the user number) can have multiple records.
Many thanks.
Update Table Ms Access
P: n/a | 'Bruce Lawrence' <dg*********@hotmail.com> wrote in message news:11*********************@g43g2000cwa.googlegro ups.com... I have a table on a SQL server called history. When I link this table
using an ODBC connection, i give it the username and password and tell
it to save the password and it works great. On my PC. Other computers
however get asked for the password each time they try to write records
to the table.
What I'm trying to do is remove the linked table and open the SQL
database in a module and use the INSERT INTO query to insert my records
and then close the DB connection.
Is this the best way to do this? Can someone provide me some sample
code that will open a SQL database using ODBC and then insert some
records into a history table and then close it all down?
I'm using Access97 and SQL 2000.
Thanks ! How is the SQL Server set up? With Windows/Built-in/Integrated security only or does it allow SQL authentication - and which do you use? It makes it easier for you if it's Windows authentication only since you don't have to worry about storing passwords, but if you use SQL authentication what do you feel about passwords and security? Should people log in each time - or could a password be stored? Finally have you considered ADO for this if there is no real need to have linked tables - just an application which does inserts. |
|