ACCESS 2000 - ODBC - MSDE

[ALMA_J_III]

Hi,

I had ACCESS project:

Two Access2003 DB. In first I had forms and reports in second - Data tables.

I have worked with Table links from form MDB to Data MDB.

But situation changed - when two and more users had connect to the data MDB,
work of forms was very slowly.

I have exported Data tables to MSDE database and made Table links as ODBC
connection to the MSDE.

I have made some code changes.

The most of functions work without problem. But I have the next problem:

When I worked with data from MDB I have used autonumber fields, after
creating of new record:

DoCmd.GoToRecord , , acNewRec

I had ID field value.

In MSDE SQL I have created same increment (identity) fields. But I haven't
new ID value.

Only after going from current to previous record ID field on form I have ID
number.

I am asking about way for retrieving new record ID from MSDE DB table after
DoCmd.GoToRecord , , acNewRec statement:

Thank's

ALMA_J_III

 

[MGFoster]

Hi,

I had ACCESS project:

Two Access2003 DB. In first I had forms and reports in second - Data tables.

I have worked with Table links from form MDB to Data MDB.

But situation changed - when two and more users had connect to the data MDB,
work of forms was very slowly.

I have exported Data tables to MSDE database and made Table links as ODBC
connection to the MSDE.

I have made some code changes.

The most of functions work without problem. But I have the next problem:

When I worked with data from MDB I have used autonumber fields, after
creating of new record:

DoCmd.GoToRecord , , acNewRec

I had ID field value.

In MSDE SQL I have created same increment (identity) fields. But I haven't
new ID value.

Only after going from current to previous record ID field on form I have ID
number.

I am asking about way for retrieving new record ID from MSDE DB table after
DoCmd.GoToRecord , , acNewRec statement:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It sounds like you are making multiple users use a single front-end,
correct? If so, don't do that. Each user should have their own
"personal" version of the front-end. Place that personal version on
their PC, or, if using some sort of Terminal Server or Citrix set up, on
their "home" folder on the server (see TS or Citrix documentation).

===

MS SQL Server puts the Identity value on the record WHILE the record is
being saved (sort of a built-in, hidden trigger). Access creates the
AutoNumber value BEFORE the record is saved.

To "see" the Identity value of a just saved record use a stored
procedure (SP) to save the record and the SQL'r built-in function
Scope_Identity() to return the record's Identity value.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQH2MLIechKqOuFEgEQKWCwCeLhbvskx2ppTK30C0Fx9xhWLTGmwAoISi
f6SnhkLzpVbJWXvq7CRYnyaC
=+K7p
-----END PGP SIGNATURE-----

 

[ALMA_J_III]

It sounds like you are making multiple users use a single front-end,

correct? If so, don't do that. Each user should have their own
"personal" version of the front-end. Place that personal version on
their PC, or, if using some sort of Terminal Server or Citrix set up, on
their "home" folder on the server (see TS or Citrix documentation).

Each user has "Front-end" with forms and reports on their personal PC-s.

MS SQL Server puts the Identity value on the record WHILE the record is
being saved (sort of a built-in, hidden trigger). Access creates the
AutoNumber value BEFORE the record is saved.

To "see" the Identity value of a just saved record use a stored
procedure (SP) to save the record and the SQL'r built-in function
Scope_Identity() to return the record's Identity value.

Thank You for answer about identity fields!

ALMA_J_III