| | |
|
|
|
SQL Server |
|---|
| message from =?Utf-8?B?Sk1vcnJlbGw=?= on 17 May 2004 |
I have a form where users enter data, which is updated to tables; from which users print reports. After using the Upsizing Wizard to create a DB in SQL Server (which sits on my pc, for testing purposes), I'm not able to enter data in one of the tables; but can in another.
Any blatant reasons for this?
tia, once again.
|
| Tony Toews replied to =?Utf-8?B?Sk1vcnJlbGw=?= on 17 May 2004 |
And to add to Van's comments Access really, really likes a RowVersion
(old name timestamp).
Tony
|
| Van T. Dinh replied to Tony Toews on 20 May 2004 |
Yep. When the Upsize Wizard offers the Upsize_ts (Upsize_TimeStamp???), I
always accept it.
|
| Van T. Dinh replied to =?Utf-8?B?Sk1vcnJlbGw=?= on 17 May 2004 |
Have you checked whether there is a PK Field in the Table?
HTH
Van T. Dinh
MVP (Access)
tables; from which users print reports. After using the
Upsizing Wizard to create a DB in SQL Server (which sits
on my pc, for testing purposes), I'm not able to enter
data in one of the tables; but can in another.
|
| =?Utf-8?B?Sk1vcnJlbGw=?= replied to Van T. Dinh on 18 May 2004 |
Yes, every table (3) upsized has a primary key assigned to it. I just finished going through the Upsizing Wizard again and ran into the same error message when trying to add records to a form: "You can't go to the specified record." The Add Record buttons on the form, and the main toolbar are also inactive.
I just noticed that the form that is working properly has a data source of a _table_ whereas the form not working has a data source of a _query_. Which begs the question; are other Access objects upsized the way tables are?
Is there an SQL tutorial that I can go through?
thank you for all your support
|
| Van T. Dinh replied to =?Utf-8?B?Sk1vcnJlbGw=?= on 19 May 2004 |
Are you using Access Database (MDB format) or Access Project (ADP format)?
|
| =?Utf-8?B?Sk1vcnJlbGw=?= replied to Van T. Dinh on 19 May 2004 |
MDB format
|
| =?Utf-8?B?Sk1vcnJlbGw=?= replied to Van T. Dinh on 19 May 2004 |
I'm working around the form issue for now.
Invalid SQL Statement. Check the server filter on the form record source.
What's going on here?
|
| Van T. Dinh replied to =?Utf-8?B?Sk1vcnJlbGw=?= on 20 May 2004 |
Well... I wouldn't recommend the ADP Project.
Microsoft recently advised that the preferred method is stil MDB format with
ODBC-linked Tables from the SQL Server.
Note that the SQL syntax is *different* from JET SQL syntax. If you use
ADP, you WILL need to check ALL Views / SP that the Upsize Wizard creates
for you. You will also have to re-create those Queries that the Upsize
Wizard can't handle. In addition, all SQL Strings in Forms / Reports / code
will need to be check.
This is NOT easy if you are only familiar with JET SQL.
|
| =?Utf-8?B?Sk1vcnJlbGw=?= replied to Van T. Dinh on 24 May 2004 |
Thanks for the advise, it is much appreciated.
|
|
Archived message: SQL Server (Microsoft Access)
