Hi Aammiz,
If I undertand your question correctly, what you need to do is just to create an extra table to tied Customer and aspnet_Membership table together. The new table should consists at least:-
Id (for simplicity you can use auto-number for this column),
UserId (datatype should similar as UserId column on aspnet_Membership, uniqueidentifier) as foreign key to link to aspnet_Membership table, and
CustId (datatype should similar as CustId on your Customer table) foreign key to link to your Customer table.
When a new user created, his login Id and Password and other information (email, role and etc) that is necessary for ASP.NET membership to function will be stored in aspnet_<tablename> tables, while those extra information (address, dob, contact no. and etc) that you require from the customer when they sign up for membership on your website will be stored in your Customer table.
I am not quite sure if you have 2 tables in 2 different databases or 2 tables in 1 database, as your reference to Customer is sometimes as a table and sometimes as a database. But, FYI, how I do it is, all the ASP.NET membership tables are on the same database as my application database. So as long as the extra table exists, there shouldn't be any issues to relate your application tables and ASP.NET membership tables.
Alternatively, you just need to use the UserId (replace CustId with UserId) as the unique Id for your Customer table to link both the tables together, by doing it this way the relationship between tables are much simpler, instead of 3 tables you just have 2 tables.
Cheers,
Eric