07. april 2006 - 13:38Der er
17 kommentarer og 1 løsning
ms sql backend
Ok... hvordan gør man, jeg har forsøgt at søge her og andre steder, men jeg kunne godt tænke mig en kort gennemgang.
Jeg har en FE/BE access db og så har jeg installeret en ms sql 2000 server personal edition. Så har jeg prøvet med noget upsizing, som jeg godt kan bruge i et databaseprojekt, men jeg er interesseret i at bruge min normale frontend. Hvis jeg forsøger at linke med noget ODBC så laver jeg en dns (ODBC 32 bit eller noget i den retning) osv osv.. men jeg kan ikke finde min backend, som jo ligger som en adp-fil!~)
Jeg er i hvert tilfald forvirret, kan nogen give mig en:
Først gør du sådan og så gør du sådan osv...
Det behøver måske ikke at blive at for teknisk jeg skal nok prøve at finde ud af noget selv, men så jeg forstår hvad jeg skal gøre!~)
Denne side indeholder artikler med forskellige perspektiver på Identity & Access Management i private og offentlige organisationer. Artiklerne behandler aktuelle IAM-emner og leveres af producenter, rådgivere og implementeringspartnere.
When you make an ADP you choose either a new SQL server database or you can choose an existing one. If you create a new table it is actually created on the SQL Server, you can edit the design of the table in Access but it IS on the SQL server. You can also create views and stored procedures, and these are also created on the SQL Server. The forms and reports etc. are stored in the Access dB. So the Access dB is the front-end and the SQL server is the backend. The tables are NOT linked via an ODBC DSN its is a connection which is stored in Access.
You can also make an MDB where you can connect via a ODBC DSN. Again the tables are stored in the SQL Server, but you can NOT design the tables in Access.
You can use the upsizing wizard to convert your Access with an Access abckend, to an Access (MDB) front-end and an SQL Server backend. you Can NOT convert an Access front-end to an Access ADP.
Actually if you have a MDB as the front-end and also an DB as th ebackend, then I think you should be able to create a ADP. Have you tried using the upsizing wizard? The ADP which it creates is only the frontend, the tables are in the SQL SERVER.
Try it!
Synes godt om
Slettet bruger
07. april 2006 - 14:48#7
I most certainly will....
Synes godt om
Slettet bruger
07. april 2006 - 14:59#8
I think it works!~)
I'll just try with a bigger db....
Synes godt om
Slettet bruger
07. april 2006 - 15:22#9
35mb of tables takes a long time...
Still waiting!~)
Synes godt om
Slettet bruger
07. april 2006 - 15:42#10
Now it came through but their was an export failure with the main table, so... I'll have to come back to this!~)
Its years since I used the upsizing wizard, back in the days of Access 97 and then I dont think ADP databases existed. There were problems converting everything in complex databases. But it should be much better in XP and 2003.
If you already have a backend (MDB) then you can use th eupsizing wizard to create them in an SQL database. You can choose to do this in the wizrad instead of creating an ADP.
You can also create them yourself in SQL Servere and then create a ODBC DSN. Then you can link to the tables in your SQL database just like you link to an MDB backend.
When you link to an SQL server dB using ODBC you can create pass-through queries which means that the SQL gets sent to the SQL server without getting parsed (checked) in Access. It has to comply to the SQL Serevers SQL syntax, not Access's. he advanatges are that it will very likley be faster because it runs on the SQL Serever and it only returns the records you ask for. You can also link to SQL Server views as though they were tables.
Synes godt om
Slettet bruger
10. april 2006 - 09:42#17
I think I have enough to get this one on the road...
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.