| Author |
 Topic Search  Topic Options
|
polecat 
Groupie
Joined: 14 April 2004
Location: Argentina
Status: Offline
Points: 131
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 09 February 2005 at 4:38pm |
|
We got no errors, but the posts don't show!!!
I mean...I can see the forums, the topics, but when I enter to a
thread, it says "There's no forum posts in this topic" or something
like that.
Anyone know what's happening???
|
|
|
 |
dj air
Senior Member
Joined: 05 April 2002
Location: United Kingdom
Status: Offline
Points: 3627
|
Post Options
Thanks(0)
Quote Reply
Posted: 09 February 2005 at 4:43pm |
|
sounds like the threds table didn't sync the Topic ID's
|
|
Ozoyo2
Newbie
Joined: 14 September 2004
Location: France
Status: Offline
Points: 12
|
Post Options
Thanks(0)
Quote Reply
Posted: 09 February 2005 at 4:56pm |
Well, after more than two weeks of total nightmare I think I managed  .
I used the method described by Borg but had to recreate all relationships and keys manually. On top of that some fields had been modified by Access' upsizing wizzard and had to be changed back (default values missing, Identity insert, etc.)
 polecat wrote:
We got no errors, but the posts don't show!!!
I mean...I can see the forums, the topics, but when I enter to a thread, it says "There's no forum posts in this topic" or something like that.
Anyone know what's happening???
|
Polecat, if you upsized from access your tblThread might be too big for the upsizing wizzard to convert it properly (it happened to me). If you look at you imported table, you will see that it is empty.
The only thing I found was to upsize from Access and then import the Thread table from Access with SQL enterprise manager.
|
|
polecat
Groupie
Joined: 14 April 2004
Location: Argentina
Status: Offline
Points: 131
|
Post Options
Thanks(0)
Quote Reply
Posted: 09 February 2005 at 5:00pm |
|
And there's any solution?
|
|
|
|
sfd19
Senior Member
Joined: 20 December 2004
Status: Offline
Points: 263
|
Post Options
Thanks(0)
Quote Reply
Posted: 09 February 2005 at 8:42pm |
-boRg- wrote:
I did look into witting an ASP application that could transfer files across, but the problem is that the primary key for many tables is an Auto number, which means if there are any deleted posts, topics, members, etc. it would screw up the transfer process.
|
I am not really firm with SQL but would it not be possible to import the Access auto-number fields as simple integers into SQL and then change these fields back to 'auto-number' (identity property that would be in SQL)?
But maybe I am missing something.
|
|
|
|
Ozoyo2
Newbie
Joined: 14 September 2004
Location: France
Status: Offline
Points: 12
|
Post Options
Thanks(0)
Quote Reply
Posted: 10 February 2005 at 2:26am |
polecat wrote:
And there's any solution? |
I did not find any solution with the Access upsize wizzard. The size is the issue. My tblThread had around 100 000 rows, I have tried with an older DB with a 1000 tblThread rows table and it worked.
What I have done (and I can't be sure it is the best solution) is to use Access to export all the tables and then use MSSQL enterprise manager to erase and import the rows in the tblThread table.
|
|
polecat
Groupie
Joined: 14 April 2004
Location: Argentina
Status: Offline
Points: 131
|
Post Options
Thanks(0)
Quote Reply
Posted: 10 February 2005 at 2:33pm |
I found the solution....
Now....my question is....in my Access forums I've added some
mods...(like the Top 10 posters, or the Member Tittle, or the birthday
mod).
Is there too much difference between the coding of the default.asp or
the register.asp of the Access version, than the SQL version???
I mean...what could happen if I upload my modified "default.asp" o
"register.asp" from the access version, to my SQL version in the server?
Could colapsate something? I'm gonna try, but if it happens, i really appreciate some explanations 
Thanx for reading!! Byeeeee 
|
|
|
|
emiduran
Newbie
Joined: 11 February 2005
Location: Argentina
Status: Offline
Points: 1
|
Post Options
Thanks(0)
Quote Reply
Posted: 11 February 2005 at 4:08pm |
Well, the solution for my:
1-Open the mdb file with Access.
2-Export the data to SQL using the "Upsize Wizard" to a new SQL Server Database (located in your computer).
3-From the local SQL-Server Export the Database to the websever SQL-Server using the third method
option for the list named like "copy objects and data between ths sql
server databases" (or similar, sorry but i have the spanish version).
4-Finally run the msSQL_server_setup.asp fila.
And ENJOY !!!!
PD: If your conection is too slow, the option 3 possible
fail. Then you will try to use a backup file
copied to the web-server and restore into a new database on the same
server.
PD: I'm sorry about my bad english 
|
|
